[PATCH v3 0/3] MCPM/TC2 support for CPU powerdown synchronisation
Nicolas Pitre
nicolas.pitre at linaro.org
Sat Oct 26 22:52:58 EDT 2013
On Fri, 25 Oct 2013, Dave Martin wrote:
> On Thu, Oct 24, 2013 at 06:19:42PM +0530, Vijay Kilari wrote:
> > Sorry. Below is the right DCC configuration for SCC 700
> > SCC: 0x700 0x0032F003 ;CFGRW48 - [25:24]Boot CPU [28]Boot
> >
> > On Thu, Oct 24, 2013 at 6:18 PM, Vijay Kilari <vijay.kilari at gmail.com> wrote:
> > > Hi Dave Martin,
> > >
> > > With the below configuration, I tried to check cpu hotplug as this
> > > is prerequisite for kexec.
> > > I see cpu hotplug fails. hot-unplug is OK but hot plug-in fails.
>
> Thanks for giving this a try.
>
> > > Below is my DCC board configuration
>
>
> I've attached my board.txt.
>
> The only obvious difference that I think should have an impact is that
> bit 13 in SCC 0x700 needs to be 1 in order for the non-boot cluster to
> be powered down on startup.
>
> In my board.txt, SCC 0x700 has the value 0x0032F003 -- you have that,
> but it's commented out.
Is there a way to programmatically determine from Linux if the necessary
bits are set?
...
Yes, from physical 0x7fff0700. I think we should test for the proper
bits to be set such as bit 12 which is absolutely needed for the code in
tc2_pm.c to work, and refuse to register the TC2 MCPM backend with a big
warning in the boot log to that effect otherwise. If Linux can flag
inproper firmware config that might help with issues like this one.
> What happens if you set that bit, and make no other changes to your
> config?
That would be interesting to know indeed.
Nicolas
More information about the linux-arm-kernel
mailing list