From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: Yao Zi <ziyao@disroot.org>, Rob Herring <robh@kernel.org>,
Chukun Pan <amadeus@jmu.edu.cn>, Jonas Karlman <jonas@kwiboo.se>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/1] arm64: dts: rockchip: rk3528: Add CPU frequency scaling support
Date: Thu, 10 Jul 2025 13:45:43 +0200 [thread overview]
Message-ID: <5025631.aeNJFYEL58@phil> (raw)
In-Reply-To: <20250620100010.1291658-2-amadeus@jmu.edu.cn>
Am Freitag, 20. Juni 2025, 12:00:10 Mitteleuropäische Sommerzeit schrieb Chukun Pan:
> By default, the CPUs on RK3528 operates at 1.5GHz. Add CPU frequency and
> voltage mapping to the device tree to enable dynamic scaling via cpufreq.
>
> The OPP values come from downstream kernel[1]. Both 408MHz and 600MHz
> frequencies use the normal PLL, so use the corresponding highest voltage.
>
> The voltage used for other frequencies can't be less than above (875mV).
> Therefore, 816MHz to 1200MHz also uses the corresponding highest voltage.
There has often been the argument that selecting a frequency that has the
same voltage as a faster frequency does not save any power.
Hence I remember that we dropped slower frequencies on other socs
that share the same voltage with a higher frequency.
>
> The remaining 1416MHz to 2016MHz use a voltage close to actual frequency.
>
> [1] https://github.com/rockchip-linux/kernel/blob/develop-5.10/arch/arm64/boot/dts/rockchip/rk3528.dtsi
>
> Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> ---
> arch/arm64/boot/dts/rockchip/rk3528.dtsi | 64 ++++++++++++++++++++++++
> 1 file changed, 64 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3528.dtsi b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> index 829f980ea353..5cb7f10b79ed 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> @@ -53,6 +53,7 @@ cpu0: cpu@0 {
> device_type = "cpu";
> enable-method = "psci";
> clocks = <&scmi_clk SCMI_CLK_CPU>;
> + operating-points-v2 = <&cpu_opp_table>;
> };
>
> cpu1: cpu@1 {
> @@ -61,6 +62,7 @@ cpu1: cpu@1 {
> device_type = "cpu";
> enable-method = "psci";
> clocks = <&scmi_clk SCMI_CLK_CPU>;
> + operating-points-v2 = <&cpu_opp_table>;
> };
>
> cpu2: cpu@2 {
> @@ -69,6 +71,7 @@ cpu2: cpu@2 {
> device_type = "cpu";
> enable-method = "psci";
> clocks = <&scmi_clk SCMI_CLK_CPU>;
> + operating-points-v2 = <&cpu_opp_table>;
> };
>
> cpu3: cpu@3 {
> @@ -77,6 +80,67 @@ cpu3: cpu@3 {
> device_type = "cpu";
> enable-method = "psci";
> clocks = <&scmi_clk SCMI_CLK_CPU>;
> + operating-points-v2 = <&cpu_opp_table>;
> + };
> + };
> +
> + cpu_opp_table: opp-table-cpu {
> + compatible = "operating-points-v2";
> + opp-shared;
> +
> + opp-408000000 {
> + opp-hz = /bits/ 64 <408000000>;
> + opp-microvolt = <875000 875000 1100000>;
> + clock-latency-ns = <40000>;
> + opp-suspend;
> + };
> +
> + opp-600000000 {
> + opp-hz = /bits/ 64 <600000000>;
> + opp-microvolt = <875000 875000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-816000000 {
> + opp-hz = /bits/ 64 <816000000>;
> + opp-microvolt = <875000 875000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1008000000 {
> + opp-hz = /bits/ 64 <1008000000>;
> + opp-microvolt = <875000 875000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1200000000 {
> + opp-hz = /bits/ 64 <1200000000>;
> + opp-microvolt = <900000 900000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1416000000 {
> + opp-hz = /bits/ 64 <1416000000>;
> + opp-microvolt = <925000 925000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1608000000 {
> + opp-hz = /bits/ 64 <1608000000>;
> + opp-microvolt = <975000 975000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1800000000 {
> + opp-hz = /bits/ 64 <1800000000>;
> + opp-microvolt = <1037500 1037500 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-2016000000 {
> + opp-hz = /bits/ 64 <2016000000>;
> + opp-microvolt = <1100000 1100000 1100000>;
> + clock-latency-ns = <40000>;
> };
> };
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>
Cc: Yao Zi <ziyao@disroot.org>, Rob Herring <robh@kernel.org>,
Chukun Pan <amadeus@jmu.edu.cn>, Jonas Karlman <jonas@kwiboo.se>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/1] arm64: dts: rockchip: rk3528: Add CPU frequency scaling support
Date: Thu, 10 Jul 2025 13:45:43 +0200 [thread overview]
Message-ID: <5025631.aeNJFYEL58@phil> (raw)
In-Reply-To: <20250620100010.1291658-2-amadeus@jmu.edu.cn>
Am Freitag, 20. Juni 2025, 12:00:10 Mitteleuropäische Sommerzeit schrieb Chukun Pan:
> By default, the CPUs on RK3528 operates at 1.5GHz. Add CPU frequency and
> voltage mapping to the device tree to enable dynamic scaling via cpufreq.
>
> The OPP values come from downstream kernel[1]. Both 408MHz and 600MHz
> frequencies use the normal PLL, so use the corresponding highest voltage.
>
> The voltage used for other frequencies can't be less than above (875mV).
> Therefore, 816MHz to 1200MHz also uses the corresponding highest voltage.
There has often been the argument that selecting a frequency that has the
same voltage as a faster frequency does not save any power.
Hence I remember that we dropped slower frequencies on other socs
that share the same voltage with a higher frequency.
>
> The remaining 1416MHz to 2016MHz use a voltage close to actual frequency.
>
> [1] https://github.com/rockchip-linux/kernel/blob/develop-5.10/arch/arm64/boot/dts/rockchip/rk3528.dtsi
>
> Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> ---
> arch/arm64/boot/dts/rockchip/rk3528.dtsi | 64 ++++++++++++++++++++++++
> 1 file changed, 64 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3528.dtsi b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> index 829f980ea353..5cb7f10b79ed 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3528.dtsi
> @@ -53,6 +53,7 @@ cpu0: cpu@0 {
> device_type = "cpu";
> enable-method = "psci";
> clocks = <&scmi_clk SCMI_CLK_CPU>;
> + operating-points-v2 = <&cpu_opp_table>;
> };
>
> cpu1: cpu@1 {
> @@ -61,6 +62,7 @@ cpu1: cpu@1 {
> device_type = "cpu";
> enable-method = "psci";
> clocks = <&scmi_clk SCMI_CLK_CPU>;
> + operating-points-v2 = <&cpu_opp_table>;
> };
>
> cpu2: cpu@2 {
> @@ -69,6 +71,7 @@ cpu2: cpu@2 {
> device_type = "cpu";
> enable-method = "psci";
> clocks = <&scmi_clk SCMI_CLK_CPU>;
> + operating-points-v2 = <&cpu_opp_table>;
> };
>
> cpu3: cpu@3 {
> @@ -77,6 +80,67 @@ cpu3: cpu@3 {
> device_type = "cpu";
> enable-method = "psci";
> clocks = <&scmi_clk SCMI_CLK_CPU>;
> + operating-points-v2 = <&cpu_opp_table>;
> + };
> + };
> +
> + cpu_opp_table: opp-table-cpu {
> + compatible = "operating-points-v2";
> + opp-shared;
> +
> + opp-408000000 {
> + opp-hz = /bits/ 64 <408000000>;
> + opp-microvolt = <875000 875000 1100000>;
> + clock-latency-ns = <40000>;
> + opp-suspend;
> + };
> +
> + opp-600000000 {
> + opp-hz = /bits/ 64 <600000000>;
> + opp-microvolt = <875000 875000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-816000000 {
> + opp-hz = /bits/ 64 <816000000>;
> + opp-microvolt = <875000 875000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1008000000 {
> + opp-hz = /bits/ 64 <1008000000>;
> + opp-microvolt = <875000 875000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1200000000 {
> + opp-hz = /bits/ 64 <1200000000>;
> + opp-microvolt = <900000 900000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1416000000 {
> + opp-hz = /bits/ 64 <1416000000>;
> + opp-microvolt = <925000 925000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1608000000 {
> + opp-hz = /bits/ 64 <1608000000>;
> + opp-microvolt = <975000 975000 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-1800000000 {
> + opp-hz = /bits/ 64 <1800000000>;
> + opp-microvolt = <1037500 1037500 1100000>;
> + clock-latency-ns = <40000>;
> + };
> +
> + opp-2016000000 {
> + opp-hz = /bits/ 64 <2016000000>;
> + opp-microvolt = <1100000 1100000 1100000>;
> + clock-latency-ns = <40000>;
> };
> };
>
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-07-10 12:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 10:00 [PATCH v2 0/1] arm64: dts: rockchip: rk3528: Add CPU frequency scaling support Chukun Pan
2025-06-20 10:00 ` Chukun Pan
2025-06-20 10:00 ` [PATCH v2 1/1] " Chukun Pan
2025-06-20 10:00 ` Chukun Pan
2025-07-10 11:45 ` Heiko Stuebner [this message]
2025-07-10 11:45 ` Heiko Stuebner
2025-07-10 12:11 ` Jonas Karlman
2025-07-10 12:11 ` Jonas Karlman
2025-07-10 15:59 ` Alexey Charkov
2025-07-10 15:59 ` Alexey Charkov
2025-07-16 14:30 ` Chukun Pan
2025-07-16 14:30 ` Chukun Pan
2025-07-16 15:48 ` Alexey Charkov
2025-07-16 15:48 ` Alexey Charkov
2025-07-17 7:00 ` Chukun Pan
2025-07-17 7:00 ` Chukun Pan
2025-07-17 8:46 ` Alexey Charkov
2025-07-17 8:46 ` Alexey Charkov
2025-07-18 14:01 ` Chukun Pan
2025-07-18 14:01 ` Chukun Pan
2025-07-18 15:03 ` Alexey Charkov
2025-07-18 15:03 ` Alexey Charkov
2025-07-20 14:00 ` Chukun Pan
2025-07-20 14:00 ` Chukun Pan
2025-07-27 17:09 ` Willy Tarreau
2025-07-27 17:09 ` Willy Tarreau
2025-07-30 7:00 ` Chukun Pan
2025-07-30 7:00 ` Chukun Pan
2025-07-30 7:11 ` Willy Tarreau
2025-07-30 7:11 ` Willy Tarreau
2025-07-30 13:20 ` Chukun Pan
2025-07-30 13:20 ` Chukun Pan
2025-07-30 13:33 ` Willy Tarreau
2025-07-30 13:33 ` Willy Tarreau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5025631.aeNJFYEL58@phil \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=ziyao@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.