Hi,
> >> >> + psci {
> >> >> + compatible = "arm,psci";
> >> >> + method = "smc";
> >> >> + cpu_off = <0x84000002>;
> >> >> + cpu_on = <0xC4000003>;
> >> >> + };
> >> >
> >> > Back at v2 you mentioned that CPU_OFF wasn't working [1].
> >> >
> >> > Do both CPU_ON and CPU_OFF work for all CPUs, including the boot CPU?
> >>
> >> The CPU1 ~ CPU7 are well woking about CPU_ON/OFF.
> >> CPU0 (boot CPU) is only well working for CPU_OFF.
> >> But when I try to turn on the CPU0 after CPU_OFF, I failed it.
> >
> > That's rather worrying. Can you look into what's going on here? I'd
> > rather not have dts describing things which are known to be broken.
>
> The board dts don't include any node for CPU_ON/OFF.
I don't understand. The CPU_ON and CPU_OFF IDs are in the psci node
quoted above, and all the CPUs had enable-method = "psci".
> When I try to turn on the CPU0 (boot CPU), fail to turn on and lockup happen.
> After lockup happen, I cannot use the console.
That sounds like a pretty major bug.
Are you able to investigate with a hardware debugger?
Do other CPUs eventually log errors regarding the lockup? Or is the
machine completely dead from this point on?
> >> > I take it CPUs boot at EL2?
> >
> > Do the CPUs boot at EL1 or EL2?
>
> Unfortunately, I cannot check the secure firmware for Exynos5433 SoC.
> I think that a few SoC provider probably would know it.
I guess I asked the wrong question.
Do CPUs enter the kernel at EL2 or at EL1?
Thanks,
Mark.
--
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
