On Mon, 8 Aug 2005, Todd Poynor wrote: > PowerOP is a system power parameter management API submitted for > discussion. PowerOP writes and reads power "operating points", > comprised of arbitrary integer-valued values, called power parameters, > that correspond to registers, clocks, dividers, voltage regulators, > etc. that may be modified to set a basic power/performance point for the > system. The core basically passes an array of integer-valued power > parameters (with very little additional structure imposed by the core) > to a platform-specific backend that interprets those values and makes > the requested adjustments. PowerOP is intended to leave all power > policy decisions to higher layers. An optional sysfs representation of > power parameters is also available, primarily for diagnostic use. What do those higher layers look like? Do you have a userspace component that uses this interface? Who is using this code? Are there vendors that are already shipping systems with this enabled? Is this part of the DPM project? If so, what other components are left in DPM? What are your plans to integrate this more with the cpufreq code? Thanks, Pat
