On Sun, 2009-02-15 at 16:44 -0800, Arjan van de Ven wrote: > On Mon, 16 Feb 2009 00:10:15 +0100 > "Rafael J. Wysocki" <rjw@xxxxxxx> wrote: > > > Hi, > > > > The recent descussion about the Android PM patches sent by Arve shows > > that there is a need to introduce a mechanism allowing us to: > > (1) automatically put the system as a whole into a sleep state (eg. > > suspend to RAM) when it is found to be "idle", where the meaning of > > "idle" has to be defined too, > > (2) put given subset of devices into low power states whenever they > > are not used, without putting the entire system into a sleep state. > > > For (2), for me the answer is very obvious: .../... I agree with pretty much everything Arjan wrote here. > Userland should never ever control the state of a device like this > directly. It should do so by a) closing the device and b) setting > latency / functional requirements With the possible exception of things like wifi/bt killswitch or network or similar where the driver cannot shut the device down without losing the ability to detect activity (ie, switch your PHY off is nice but you lose the ability to monitor the link for example). Cheers, Ben. _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
