> > > I have some notion that a policy manager can create a state with > simple > > > & general names like fast, medium, slow (whatever) which is the > > > interface in which applications might speak. A complex policy > > > manager > > > > ...which is very bad interface for applications. See my other > > mail. Applications should not have to play with fast/medium/slow, > > explicitely. Instead, on opening /dev/dsp, you should power up the > > sound system (and maybe adjust cpu frequency if > > neccessary). Application should not have to do echo fast > somewhere > > before opening /dev/dsp > > How does /dev/dsp know at what level it can run at? On the SOC I > control the speed of the DSP. I can adjust its MIPs rate. (I meant /dev/dsp -- OSS audio device, not Digital Signal Processor). > A missing pieces is meaningful coordination between devices. Each > device is not an island. Not taking care of all devices on the internal > interconnects may mean you don't get the big power savings. For the DSP For notebooks, devices *are* islands. powerop tries to push everything-depends-on-everything model that may be good for some SoC, but sucks for notebooks. We need some middle ground. -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
