On Fri, Dec 31, 2010 at 11:01:08AM +0100, Jean-Yves Migeon wrote: > On 31.12.2010 10:36, Jukka Ruohonen wrote: > > Module Name: src > > Committed By: jruoho > > Date: Fri Dec 31 09:36:15 UTC 2010 > > > > Modified Files: > > src/etc/powerd/scripts: sleep_button > > > > Log Message: > > Use hw.acpi.sleep.state instead of machdep.sleep_state. > > And so it begins :) > > I am using machdep.sleep_state as node to put a domU into suspend mode. > Up to now, putting sleep_state under machdep allowed powerd(8) > sleep_button to be used regardless of the environment (eg. ACPI sleep or > Xen domU sleep). > > While retiring sleep_state from machdep goes in the right direction > IMHO, will it be replaced by a MI interface to put a system into sleep, > as it is not a feature specific to ACPI?
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. 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. Dave -- David Young OJC Technologies dyo...@ojctech.com Urbana, IL * (217) 278-3933
