On Tue 2009-02-10 06:10:24, Woodruff, Richard wrote: > > > From: linux-pm-bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx [mailto:linux-pm- > > bounces@xxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Pavel Machek > > Sent: Tuesday, February 10, 2009 5:18 AM > > > Plus I don't like that any application select-ing on input device can > > prevent system from sleeping. That's quite a unexpected sideeffect. > > Not sure this is your point. But when doing PowerTop based debug in our Linux userspace we found several applications using select() (or some variant) with a much short timeout than needed. In effect they were polling and keeping the system alive. > > In the cases it was an application in our control we converted it to something sane. > No, that's something different. Apparently, on android, if there's event ready on one of the input devices, system will not go to sleep. That's quite an "interesting" behaviour. Heh, they could rely on it and get rid of the wakelock. Just create strange device that disallows system sleep when you select() on it, and allows it when you read() from it :-). 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