Thread (53 messages) 53 messages, 11 authors, 2006-01-13

Re: [patch] pm: fix runtime powermanagement's /sys interface

From: Adam Belay <hidden>
Date: 2006-01-07 12:43:16
Also in: lkml

On Sat, Jan 07, 2006 at 11:25:54AM +0100, Pavel Machek wrote:
quoted
quoted
I asked for an example.
Look at the ACPI spec, it has several examples...

1.) most sound cards have more than two states. (once again latency over
power savings trade offs)
What is the latency in typical "most sound card" case?
ACPI requires within 100ms for D1 and D2.  D3 can be longer.
quoted
4.) IDE hard drives and other storage media have "sleep", "suspend",
etc.
Yep; but spindown takes 5 seconds, so if you need to reset ide bus or
not to get it back is driver detail. Plus notice how power consuption
in sleep and suspend is almost same; motor not running is big deal
there. Ouch and hdparm already handles these.
5 seconds is more of an upper bound.  My laptop hardrive can do spindown
and spinup in around 1 second.  hdparm doesn't handle the deeper suspend
case (it can enter but not recover).  Kernel level support is required.
quoted
6.) many video cards implement D1 and D2 as you've already seen.  This
is often more a matter of "we only know how to restore from such and such
states"
Excatly, so "on"/"off" is enough for them.
Not really.  The ACPI spec suggests latency requirements for each state.
If we had better drivers, we might enter a lower latency video card
state when the screen is blanked that's not quite an "off" state.

The ACPI spec also defines intermediate states for input devices,
various display classes, and modems.

-Adam

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help