[lkml]   [2011]   [Oct]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH v2 1/7] clk: Add a generic clock infrastructure
    On Fri, Oct 14, 2011 at 04:10:26PM +0800, Richard Zhao wrote:
    > On Thu, Sep 22, 2011 at 03:26:56PM -0700, Mike Turquette wrote:

    snip essentially Mike's entire mail - *please* delete irrelevant quotes
    from your replies, it makes it very much easier to find the new text in
    your mail and is much more friendly to people reading mail on mobile

    > > +static int __clk_enable(struct clk *clk)
    > > +{

    > Could you expose __clk_enable/__clk_disable? I find it hard to implement
    > clk group. clk group means, when a major clk enable/disable, it want a set
    > of other clks enable/disable accordingly.

    Shouldn't this be something the core is implementing? I'd strongly
    expect that the clock drivers are relatively dumb and delegate all the
    decision making to the core API. Otherwise it's going to be hard for
    the core to implement any logic that involves working with more than one
    clock like rate change notification, or guarantee that driver requests
    made through the API are satisfied, as the state of the clocks will be
    changing underneath it.

     \ /
      Last update: 2011-10-14 12:07    [W:0.030 / U:0.048 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site