Re: Attempted summary of suspend-blockers LKML thread
Date: Wed Aug 04 2010 - 19:50:28 EST
On Wed, 4 Aug 2010, Paul E. McKenney wrote:
On Wed, Aug 04, 2010 at 04:23:43PM -0700, david@xxxxxxx wrote:
On Wed, 4 Aug 2010, Arve Hj?nnev?g wrote:
We suspend as soon as no wakelocks are held. There is no delay.
So, if I have a bookreader app that is not allowed to get the
wakelock, and nothing else is running, the system will suspend
immediatly after I click a button to go to the next page? it will
not stay awake to give me a chance to read the page at all?
how can any application run without wakelock privilages?
Isn't a wakelock held as long as the display is lit, so that the
system would continue running as long as the page was visible?
what holds this wakelock, and what sort of timeout does it have? (and why
could that same timeout be used in other ways instead)
how many apps really need to keep running after the screen blanks? there
are a few (audio output apps, including music player and Navigation
directions), but I don't have see a problem with them being marked as the
'trusted' apps to pay attention instead.
if the backlight being on holds the wakelock, it would seem that almost
every other use of the wakelock could (and probably should) be replaced by
something that tickles the display to stay on longer.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/