From: Alexander Shiyan <[email protected]> During system boot, the cpufreq driver reports unlisted initial frequencies: cpufreq: cpufreq_policy_online: CPU0: Running at unlisted initial frequency: 900000 kHz, changing to: 1200000 kHz cpufreq: cpufreq_policy_online: CPU4: Running at unlisted initial frequency: 816000 kHz, changing to: 1200000 kHz cpufreq: cpufreq_policy_online: CPU6: Running at unlisted initial frequency: 816000 kHz, changing to: 1200000 kHz
Add assigned-clock-rates to the SCMI clock controller node in the device tree to establish proper initial frequencies. This ensures all CPU cores boot at valid frequencies that match the cpufreq policy, eliminating the warning messages and unnecessary frequency changes during initialization. Signed-off-by: Alexander Shiyan <[email protected]> Link: https://lore.barebox.org/[email protected] Signed-off-by: Sascha Hauer <[email protected]> (cherry picked from commit 1b91aafee348423090c1347307674fd17729c00c) Signed-off-by: Ahmad Fatoum <[email protected]> --- arch/arm/dts/rk3588.dtsi | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/arch/arm/dts/rk3588.dtsi b/arch/arm/dts/rk3588.dtsi index 667dd0c5a873..416700cf0ecd 100644 --- a/arch/arm/dts/rk3588.dtsi +++ b/arch/arm/dts/rk3588.dtsi @@ -8,7 +8,12 @@ dmc: memory-controller { }; &scmi_clk { - assigned-clocks = <&scmi_clk SCMI_CLK_CPUB01>, - <&scmi_clk SCMI_CLK_CPUB23>; - assigned-clock-rates = <816000000>, <816000000>; + assigned-clocks = + <&scmi_clk SCMI_CLK_CPUL>, + <&scmi_clk SCMI_CLK_CPUB01>, + <&scmi_clk SCMI_CLK_CPUB23>; + assigned-clock-rates = + <1200000000>, + <1200000000>, + <1200000000>; }; -- 2.47.3
