> >> - 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 -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
