On Tue, Jul 08, 2014 at 02:39:37PM +0100, Abhilash Kesavan wrote: > Hi Lorenzo, > > On Tue, Jul 8, 2014 at 4:23 PM, Lorenzo Pieralisi > <lorenzo.pieralisi@xxxxxxx> wrote: > > On Fri, Jul 04, 2014 at 10:21:56PM +0100, Abhilash Kesavan wrote: > >> On Sat, Jul 5, 2014 at 2:30 AM, Nicolas Pitre <nicolas.pitre@xxxxxxxxxx> wrote: > >> > On Sat, 5 Jul 2014, Abhilash Kesavan wrote: > >> > > >> >> Use the MCPM layer to handle core suspend/resume on Exynos5420. > >> >> Also, restore the entry address setup code post-resume. > >> >> > >> >> Signed-off-by: Abhilash Kesavan <a.kesavan@xxxxxxxxxxx> > >> > > >> > Acked-by: Nicolas Pitre <nico@xxxxxxxxxx> > >> This is one of the last missing bits for exynos MCPM. Thanks for your > >> patient reviews of all the exynos mcpm back-end patches. > > > > Sorry for the delay in getting back to you. > Thanks for your comments. > > > > You still need to handle the residency parameter in the MCPM suspend call > > properly to differentiate between core gating and cluster gating. > I am not too familiar with the cpuidle driver, but I see only cluster > power off state listed in the bL cpuidle driver. > > > > CPUidle might want to request a state that allows for core gating > > residency but not cluster gating one, in that case the last man > > standing must not shutdown the cluster. > For this, I would have to add another state to the bL cpuidle driver > or migrate to using your under-review generic idle state patchset. > Then based on the residency value skip/do cluster power down. Is this > correct ? > > > > This must be handled in the power down function, and it can be done > > in a separate patch since it is an optimization. Current MCPM interface has > > all it is needed to handle this properly, and I am keen on patching the > > CPUidle bL driver to pass the actual residency instead of hardcoding it > > to 0 (ie on TC2 it was not needed, no core gating). > I will look at doing this once the s2r patch gets merged. Ok, let's get it done once the CPUidle bL driver DT version gets merged, I will add a patch that passes the proper residency and you can patch the MCPM back-end then, until then CPUidle will be suboptimal but I guess we can live with that for now. Thanks, Lorenzo -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html