On Thu, Dec 04, 2014 at 12:58:21PM +0530, Shreyas B. Prabhu wrote: > From: "Preeti U. Murthy" <[email protected]> > > The secondary threads should enter deep idle states so as to gain maximum > powersavings when the entire core is offline. To do so the offline path > must be made aware of the available deepest idle state. Hence probe the > device tree for the possible idle states in powernv core code and > expose the deepest idle state through flags. > > Since the device tree is probed by the cpuidle driver as well, move > the parameters required to discover the idle states into an appropriate > common place to both the driver and the powernv core code. > > Another point is that fastsleep idle state may require workarounds in > the kernel to function properly. This workaround is introduced in the > subsequent patches. However neither the cpuidle driver or the hotplug > path need be bothered about this workaround. > > They will be taken care of by the core powernv code. > > Originally-by: Srivatsa S. Bhat <[email protected]> > Signed-off-by: Preeti U. Murthy <[email protected]> > Signed-off-by: Shreyas B. Prabhu <[email protected]>
Reviewed-by: Paul Mackerras <[email protected]> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
