Messages in this thread |  | | Date | Tue, 11 May 2010 17:45:54 +0100 | | From | Matthew Garrett <> | | Subject | Re: [PATCH 0/8] Suspend block api (version 6) |
| |
On Tue, May 11, 2010 at 09:36:33AM -0700, Tony Lindgren wrote: > OK, so can the suspend blocker then become just: > > # Block suspend while idle, system stays running > # echo default > /sys/power/policy > > and the when it's OK to suspend: > > # Allow suspend while idle, system suspends when it hits kernel idle loop > # echo opportunistic > /sys/power/policy > > or do you still need something more to ensure the data gets into your > app and be handled?
Yes. You still need suspend blocks.
> The part I really don't like is the idea of patching all over the drivers > and userspace for the wakelocks/suspendblocks.
I don't like the idea either, but given that nobody has actually provided any other ideas that would actually work then I don't think we've got a great deal of choice.
-- Matthew Garrett | mjg59@srcf.ucam.org
|  |