On Thursday 26 July 2012 04:13 AM, Kevin Hilman wrote:

Tero Kristo[off-list ref]  writes:

quoted

quoted

 On Fri, 2012-07-20 at 13:38 +0530, Rajendra Nayak wrote:

quoted

quoted

 On Friday 20 July 2012 12:55 PM, Shilimkar, Santosh wrote:

quoted

 >  On Fri, Jul 20, 2012 at 11:34 AM, Rajendra Nayak[off-list ref]   wrote:

quoted

 >>  pwrdm_pre_transition()/pwrdm_post_transition() have always been high latency
 >>  operations done within cpuidle to do Powerdomain level book-keeping to know
 >>  what state transitions for different Powerdomains have been triggered.
 >>  This is also useful to do a restore-on-demand in some cases when we know
 >>  the context for the given Powerdomain was lost etc.
 >>
 >>  Now that we have definitive entry/exit points (thanks to the Powerdomain
 >>  level usecounting) for Powerdomain transitions, these book-keeping functions
 >>  can very well be moved from within CPUidle into pwrdm_clkdm_enable()/pwrdm_
 >>  clkdm_disable() functions.
 >>
 >>  Also rename _pwrdm_pre/post_transition_cb() to pwrdm_pre/post_transition()
 >>  and get rid of the original ones which iterate over all powerdomains.
 >>
 >>  Signed-off-by: Rajendra Nayak[off-list ref]

This is excellent!   Thanks for working on this.

However, it needs a rebase against mainline though because I merged a
set of optimizations[1] to this code already that only calls pre/post
per-pwrdm.

Sure Kevin, I'll repost this series once 3.6-rc1 is out.