[lkml]   [2010]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: suspend blockers & Android integration
On Thu, Jun 3, 2010 at 4:23 PM, Ingo Molnar <> wrote:
>  - Controlled auto-suspend: drivers (such as input) could on wakeup
>   automatically set the 'minimum wakeup latency' value of wakee tasks to a
>   lower value. This automatically prevents another auto-suspend in the near
>   future: up to the point the wakee task increases its latency (via the
>   scheduler syscall) again and allows suspend again.

How do you clear the latency value in a safe way? If another wakeup
event happens right after your wakee task is done processing the last
event and decides to increase its latency, auto suspend will be
allowed even though you have an unprocessed wakeup event. Also how do
you know which task will read the event if it is not already waiting
for it?

>   This means there will be no surprise suspends for a task that may take a
>   bit longer than usual to finish its work. [ Detail: this would only be done
>   for tasks that have a non-default (non-infinity) task->latency value - to
>   prevent the input driver from lowering latency values (and preventing
>   future suspends) just because some unaware apps are running and using input
>   drivers. ]

Don't you need two inifinity values for this?

Arve Hjønnevåg
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2010-06-04 06:57    [from the cache]
©2003-2014 Jasper Spaans. hosted at Digital Ocean