Santosh Shilimkar <santosh.shilimkar@xxxxxx> writes: > Kevin, > > On Wednesday 13 February 2013 02:25 PM, Santosh Shilimkar wrote: >> Current CPU PM code code make use of common cpu_suspend() path for all the >> CPU power states which is not optimal. In fact cpu_suspend() path is needed >> only when we put CPU power domain to off state where the CPU context is lost. >> >> Update the code accordingly so that the expensive cpu_suspend() path >> can be avoided for the shallow CPU power states like CPU PD INA/CSWR. >> >> The patch has been tested on OMAP4430 and OMAP5430(with few out of tree patches) >> devices for suspend and CPUidle. >> >> Cc: Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> >> >> Reported-by: Richard Woodruff <r-woodruff2@xxxxxx> >> Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx> >> --- >> Update changelog to include testing details as suggested >> by Kevin Hilman. >> > Ping. > It can get into rc's but since it is not strict regression, > and if it has to wait for 3.10 then I can add this one > along with rest of the PM patches posted towards 3.10 > > Either way, let me know. I have this updated one queued for v3.10 in my PM cleanup branch (for_3.10/cleanup/pm) Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
