[lkml]   [2009]   [Jan]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH F 06/12] OMAP2/3 clock: every clock must have a clkdm
    On Wed, Jan 28, 2009 at 12:35:15PM -0700, Paul Walmsley wrote:
    > Every OMAP2/3 clock must now have an assigned clockdomain, so we can
    > remove the checks from clk_enable()/clk_disable(). Instead, verify
    > that the clockdomain is present only at clock init time via the
    > arch_clock clk_register() hook.

    I don't see the point of requiring all clocks to have a clockdomain field.
    Given that we have virtual clocks, it is quite reasonable for some clocks
    not to have a clock domain associated with them.

    The overhead for avoiding this requirement isn't that great, and I feel
    that there's little benefit from this change.

     \ /
      Last update: 2009-01-31 15:11    [W:0.019 / U:8.736 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site