On Tue, 2006-08-15 at 15:04 -0400, ext Dave Jones wrote: > > > d. In the end, all this is leading to an interface for a user-space > > policy manager that will control _system_ power state based on > > constraints imposed by HW peripherals or on policies implemented by > > device manufacturer/distro maintainer. > > How does that interface look from a userspace point of view ? > Hopefully not anything like the tuple described above. > Why would userspace ever care about "interconnect freq" ? > > Userspace cares about "save power" or "go fast". > Historically, I wish we had never exposed frequencies, but instead > a performance percentage, so that the various userspace tools > didn't have to care about things like 'what frequencies are > available'. > Adding the same mistake for voltages doesn't strike me as a fantastic > idea. The userspace interface in Eungeny's patches is for other userspace programs (policy managers) to activate/deactivate valid operating points in the system dynamically and if necessary, introduce new ones into the system. It will also allow the operating points to be referenced by name instead of the tuple. Then, we will be able to use names like 'video', 'mp3', 'fast', 'powersave', 'usb' to switch to the relevant operating point based on configuration of the policy manager. Regards, Amit -- Amit Kucheria <amit.kucheria at nokia.com> Nokia
