On Mon 2009-02-16 23:13:24, Matthew Garrett wrote: > On Mon, Feb 16, 2009 at 11:58:31PM +0100, Pavel Machek wrote: > > > If no devices are being used, and next wakeup is far enough in the > > future, just put system to sleep. Long enough == so far away that > > suspend/wakeup is short compared to that... like 20 seconds on PC. > > This is intrinsically difficult with PCs, since we have such a poorly > defined set of wakeup events. We can't wakeup on generic network > traffic, just WoL. At least e1000 in thinkpad can wakeup on generic network traffic. If particular network card can't, you just can't sleep when network is up. > Many machines won't wake up on keyboard events. Too bad. You'll have to close the lid for autosuspend to work on such hw. (Or maybe you can do some hack telling the kernel to suspend anyway if just keyboard prevents it.) > Meanwhile, on embedded it's becoming a less interesting problem because > idle and suspended are often now equivalent states. Android people tell us otherwise. 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
