[Pavel Machek <pavel@xxxxxx>] > > On Thu, Jan 29, 2009 at 5:04 AM, Pavel Machek <pavel@xxxxxx> wrote: > > > AFAICT, this is something very different. It is attempt to do > > > autosuspend right. Imagine burning cd... right now you can suspend, > > > and it will just stop the burn. > > > > > > Wakelocks code allows you to tell the machine 'feel free to suspend > > > when you have nothing to do'... so the machine will burn the cd and > > > then suspend. ... > > I don't get it. So you are running userspace while system is > suspended? The general idea is that we aggressively try to be suspended as much as possible. Typically this means that when the display is turned off (after the user inactivity timeout, managed from a userspace process), suspend is requested. If work is being done that requires the system to keep running, a wakelock is held, preventing suspend from happening. If suspend happens, but we resume due to a wakeup interrupt (for example, user pressing a key), a wakelock is typically acquired during the interrupt handler (which is called while we're resuming) and arranged to be held until the event is delivered to userspace. The userspace code which receives events acquires a wakelock before draining the queue (after select returns, before reading, etc) so that it keeps the system awake until the event is processed. In many cases the system pretty rapidly drops wakelocks and returns to suspend state. Brian _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
