Power management vs. activities (was: Re: [Sugar-devel] stopwatch activity)

[Sascha Silbe]

On Tue, Apr 27, 2010 at 11:00:15PM -0400, Benjamin M. Schwartz wrote:

> I'm reluctant to do this, though, because it feels  like an ugly hack. 
>   The right solution would be for the suspend system  to recognize 
> that Stopwatch has a timer set to expire in 100 ms, and  postpone 
> suspend.
UPower has a DBus API to set "latency requirements" [1,2]. The UPower 
backend code uses the kernel PM QoS interface [3] to set the requested 
CPU (DMA) latency (in µs, up to ~35 minutes) and network throughput (in 
kbps). cpuidle hooks into the PM QoS framework to provide CPU latency 
management.

We could use the UPower API in activities and provide a helper daemon 
for powerd to implement this API on the XO until the kernel can do 
automatic suspends.


[1] http://upower.freedesktop.org/docs/QoS.html
[2] 
http://blogs.gnome.org/hughsie/2008/11/06/devicekit-power-latency-control/
[3] Documentation/power/pm_qos_interface.txt in kernel sources
[4] http://www.celinux.org/elc08_presentations/elc2008_pm_qos_slides.pdf

CU Sascha

-- 
http://sascha.silbe.org/
http://www.infra-silbe.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: Digital signature
URL: <http://lists.laptop.org/pipermail/devel/attachments/20100428/0f8ae07c/attachment.sig>