On Mon, Feb 16, 2009 at 11:13:24PM +0000, 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. Many machines won't wake up on keyboard events. > Meanwhile, on embedded it's becoming a less interesting problem because > idle and suspended are often now equivalent states. Concentrating on > runtime PM of as much hardware as possible is arguably more interesting > for the majority of use cases. Putting the wake on key event issue aside, is it possible to have wake up's on the ms time scale? I ask because I thought the XO did exactly this (but left the screen live). Why does it take 20 sec to get into or out of S3 on my laptop? --mgross > > -- > Matthew Garrett | mjg59@xxxxxxxxxxxxx _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
