[lkml]   [2010]   [Jun]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [linux-pm] suspend blockers & Android integration
    On Wed, 9 Jun 2010 wrote:

    > why could the suspend blocker process see all events, but the power
    > manager process not see the events?
    > have the userspace talk to the power manager the way it does to the
    > suspend blocker now and what's the difference?
    > effectivly think s/suspend blocker/power manager/ (with the power manager
    > doing all the other things that are proposed instead of grabbing the
    > wakelock), the difference should be hidden to the rest of userspace.
    > what am I missing here?

    The main difference is that with a userspace power manager, programs
    have to tell the power manager whenever they open or close a
    wakeup-capable device file (and send it a copy of the file descriptor).
    With an in-kernel implementation these extra steps aren't needed,
    because of course kernel drivers already know when their device files
    are opened or closed.

    Alan Stern

     \ /
      Last update: 2010-06-10 16:43    [W:4.523 / U:0.000 seconds]
    ©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site