lkml.org 
[lkml]   [2018]   [Feb]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v2 06/16] arm64: dts: mt7622: add cpufreq related device nodes
On 06-02-18, 17:52, sean.wang@mediatek.com wrote:
> cpus {
> #address-cells = <2>;
> #size-cells = <0>;
> @@ -26,6 +70,10 @@
> device_type = "cpu";
> compatible = "arm,cortex-a53", "arm,armv8";
> reg = <0x0 0x0>;
> + clocks = <&infracfg CLK_INFRA_MUX1_SEL>,
> + <&apmixedsys CLK_APMIXED_MAIN_CORE_EN>;
> + clock-names = "cpu", "intermediate";
> + operating-points-v2 = <&cpu_opp_table>;
> enable-method = "psci";
> clock-frequency = <1300000000>;
> };
> @@ -34,6 +82,7 @@
> device_type = "cpu";
> compatible = "arm,cortex-a53", "arm,armv8";
> reg = <0x0 0x1>;
> + operating-points-v2 = <&cpu_opp_table>;
> enable-method = "psci";
> clock-frequency = <1300000000>;
> };

Sorry for not picking this earlier, but you should probably add the same clock
related properties for both cpu nodes here. Things will break if CPU1 is used by
the cpufreq core to bring the cpufreq policy online.

This can happen if cpufreq driver is a module, CPU0 is hotplugged out and then
the cpufreq driver is inserted.

--
viresh

\
 
 \ /
  Last update: 2018-02-07 04:34    [W:0.067 / U:4.844 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site