On Friday, 30. January 2009, Pavel Machek wrote: > > >> - The user-space input-event thread returns from read. It determines > > >> that the key should not wake up the system, releases the > > >> process-input-events wakelock and calls select or poll. > > > > > > This makes no sense. If the system wasn't asleep to begin with, how > > > could the key wake it up? And if the system _was_ asleep to begin > > > with, how could all of this happen without waking the system up? > > > > What I mean here is that the screen turns on and the system does not > > immediately go back to sleep. The user-space framework has its own > > idea of whether the system is awake or not. I can change this to > > "fully wake up" or "turn on the screen". > > "turn on the screen", please. (But I still don't quite get it; screen > should be at full control of userspace, so why is kernel interaction > needed?) Pavel > Turning on the screen is only on thing userspace can do. What exactly happens is beyon the scope of the kernel interface. The right term is probably something like "break out of auto-suspend" or "wake from auto suspend". -- ------- ROAD ...the handyPC Company - - - ) ) ) Uli Luckas Head of Software Development ROAD GmbH Bennigsenstr. 14 | 12159 Berlin | Germany fon: +49 (30) 230069 - 62 | fax: +49 (30) 230069 - 69 url: www.road.de Amtsgericht Charlottenburg: HRB 96688 B Managing director: Hans-Peter Constien _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
