[lkml]   [2011]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [RFC PATCH v2 1/3] PM / Core: suspend_again callback for device PM.
On Tue, Apr 26, 2011 at 01:47:21PM +0200, Rafael J. Wysocki wrote:
> Moreover, I'm not sure if kernel subsystems (including drivers) should really
> decide when to generate wakeup signals in the first place. Generally,
> user space decides what devices should wake up the system from sleep and the
> kernel should follow. So, there shouldn't be any wakeup signals enabled
> beyond what user space has requested.

The RTC wakeup signals are ok though, right? Userspace is the one
asking for that from what I can tell.

> To conclude, I'm not sure about the approach. In particular, I'm not sure
> if the benefit is worth the effort and the resulting complications (ie. the
> possibility of having to deal with wakeup signals not requested by user
> space) seem to be a bit too far reaching.
> Greg, what do you think?

I agree with you in that I don't think that this type of feature is
valid at the moment.

I don't understand why our current situation doesn't work, what are we
lacking that is needed for these systems that we have not seen before?

What is the root problem that this is trying to solve?


greg k-h

 \ /
  Last update: 2011-04-26 15:31    [W:0.100 / U:6.660 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site