> > I guess it just defines an appropriate policy. You can call it > > 'usb_mp3' if you wish ;) > > I don't think it's too embedded-specific. > > Well, it leads to exponential number of policies -- not nice. Having > usb_mp3_fileserver_webserver is not nice. To some extent having lots of specific policies in the embedded space is inevitable. The hardware is very tightly coupled. You may have almost all the functionality of a PC some 5 years back on a single chip. In that kind of environment not taking into account the chip as a whole means you do power at a 10x or say 100x of optimal. You don't get the big interconnect savings unless you link the all the individual device states with the processor states. A 400mA at 1.3v might sound good to a PC centric person, but when the design target is 4mA at 1.3v it is not good. 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 will associate this name with device and cpu states in great detail. A more general purpose one only need map it to some governor and its run time parameters. Regards, Richard W.
