lkml.org 
[lkml]   [2011]   [Jan]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: Locking in the clk API
    On Thu, Jan 20, 2011 at 08:12:45PM -0800, Saravana Kannan wrote:
    > In my opinion, the only major reason for needing atomic clk APIs was due
    > to device_ops->suspend being atomic. Since that's not the case anymore,
    > I really don't see a justification for atomic clocks. Sure, I might have
    > missed some exceptions, but in that case we should make the atomic APIs
    > an exception (add clk_enable_atomic) and not the norm.

    The suspend method has never been atomic. It has always been able to
    sleep. You're mistaken.


    \
     
     \ /
      Last update: 2011-01-21 10:35    [W:0.019 / U:31.540 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site