Re: [Dynamicpower-devel] DPM review

[Matthew L. <ml...@em...>]

As Todd mentioned, there are a lot of details and the only 
documentation is the stuff you've seen.   Here is a quick summary 
starting from the top:

Policies are a mapping of operating points to operating states.
Linux changes the operating state using the dpm_set_os function which 
is placed in the idle loop and scheduler by default.
When the operating state is changed, dpm will switch to the operating 
point that is mapped to that operating state.
It is expected that people will define additional operating states and 
add dpm_set_os in the right place to trigger the transition.
Device constraints are not mandatory.

Note;  I left out classes for simplicity.  They may or may not be 
necessary depending your device.

On Aug 17, 2005, at 2:39 AM, Livio Tenze wrote:

> Hi all!
>
> I am new in the DPM field. I would like to find a good document to 
> learn the DPM functionalities? May you suggest me?
> I read some articles and part of montavista documentation, but some 
> subjects are not clear: in particular I do not understand how the DPM 
> changes the operationg point. I am working on a freescale MX21 
> processor: I set the operating point, the operating classes and the 
> policies. When I enable a policy, how does the system change the 
> operating state? According to which rule?
> Is it mandatory to set the the device constraints?
>
> Thanks to all!
> Livius
>
>
> -------------------------------------------------------
> SF.Net email is Sponsored by the Better Software Conference & EXPO
> September 19-22, 2005 * San Francisco, CA * Development Lifecycle 
> Practices
> Agile & Plan-Driven Development * Managing Projects & Teams * Testing 
> & QA
> Security * Process Improvement & Measurement * 
> http://www.sqe.com/bsce5sf
> _______________________________________________
> Dynamicpower-devel mailing list
> Dyn...@li...
> https://lists.sourceforge.net/lists/listinfo/dynamicpower-devel
>