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: The Device Driver needs to make the decision to put the device to sleep. There are no ifs and buts about this. It's the driver who a) knows if there's any activity, such as open users and b) is in the right position to know how to put things to sleep. Of course, the subsystem the driver belongs to can provide helpers (such as generic activity timeout handlers etc). For many cases, the drivers do this today already. There are cases where doing this has side effects, mostly in terms of latency. It is reasonable to have a general mechanism that provides a central mechanism to track tolerable latencies; in fact PMQOS provides this on a high level, and I can imagine that PMQOS needs to be extended to provide a wider range of type of latencies. 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. -- Arjan van de Ven Intel Open Source Technology Centre For development, discussion and tips for power savings, visit http://www.lesswatts.org _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
