Hi Sudeep,
On Thu, Oct 5, 2017 at 5:04 PM, Sudeep Holla <sudeep.holla@xxxxxxx> wrote:
> On 05/10/17 14:26, Simon Horman wrote:
>> From: Dien Pham <dien.pham.ry@xxxxxxxxxxxxxxx>
>>
>> Current, OPP tables are defined temporary,
>> they are being evaluated and adjust in future.
>> --- a/arch/arm64/boot/dts/renesas/r8a7796.dtsi
>> +++ b/arch/arm64/boot/dts/renesas/r8a7796.dtsi
>> @@ -46,6 +46,8 @@
>> power-domains = <&sysc R8A7796_PD_CA57_CPU0>;
>> next-level-cache = <&L2_CA57>;
>> enable-method = "psci";
>> + clocks =<&cpg CPG_CORE R8A7796_CLK_Z>;
>> + operating-points-v2 = <&cluster0_opp>;
>> };
>>
>> a57_1: cpu@1 {
>> @@ -55,6 +57,7 @@
>> power-domains = <&sysc R8A7796_PD_CA57_CPU1>;
>> next-level-cache = <&L2_CA57>;
>> enable-method = "psci";
>
> Just curious why clocks are not specified in secondaries ?
Thanks for noticing, it would indeed be good to describe the clock dependency
for all CPU cores.
> Does this continue work if I hotplug out CPUs in ascending order and
> then hotplug back in descending order ? Also the current driver or OS
> may deal with that but not a good assumption when write DT
Yes that works, as Linux doesn't handle CPU hotplug details.
CPU hotplug is controlled by PSCI, i.e. out of control of the Linux kernel.
So it doesn't matter at all what is described here ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
