On Thursday 27 July 2006 7:43 am, Alan Stern wrote: > > Proper runtime power management requires drivers to change their > devices' power states as needed, with no intervention of the PM > core. Neither power/state nor power.power_state.event is really > necessary for this purpose. That's a key point that I think was not widely understood early on. The driver APIs exist to make sure systems can be cleanly shut down ... not to reduce power usage. At best, that sysfs power/state thing is a big distraction from actually trying to make drivers be power-efficient. See list archives for the "RFC -- updated Documentation/power/devices.txt" thread; one of my last posts there has a version of that document with lots of examples of how runtime power saving works; it does NOT need to involve any kind of public power state updating. Things like cpufreq and dynamic tick, or power-aware idle tasks, don't need to change externally visible state any more than per-device power saving policies do. - Dave
