On 31.12.2010 19:51, David Young wrote: > IMO, we should put the system to sleep by sending a > power-saving/wakeup-latency goal and a set of waking events (e.g., > keystroke, mouse movement, LAN activity) to the root device_t using > drvctl. To put any smaller set of devices to sleep, send the goal & > wake events to some subtree.
I haven't looked at the details of the ioctl(), but I would expect it to be used against /dev/drvctl, no? This seems plausible to me; at least, suspend/sleep should be part of pmf(9) (even in my Xen's case, all driver sleep/wake coded uses pmf(9)). > FWIW, the sleep states that ACPI names are not sufficient even to > describe all of the potential sleep states of ACPI hardware. I have a > laptop that's perfectly capable of an "S3-like" sleep, but the ACPI BIOS > doesn't support S3, and the HDD is not formatted properly for the S4 > sleep. -- Jean-Yves Migeon jeanyves.mig...@free.fr
