From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Alexey Charkov <alchark@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Alexey Charkov <alchark@gmail.com>
Subject: Re: [PATCH 1/4] arm64: dts: rockchip: list all CPU supplies on ArmSoM Sige5
Date: Wed, 04 Jun 2025 20:38:03 +0200 [thread overview]
Message-ID: <6656934.DvuYhMxLoT@workhorse> (raw)
In-Reply-To: <20250603-sige5-updates-v1-1-717e8ce4ab77@gmail.com>
On Tuesday, 3 June 2025 19:01:13 Central European Summer Time Alexey Charkov wrote:
> List both CPU supply regulators which drive the little and big CPU
> clusters, respectively, so that cpufreq can pick them up.
>
> Signed-off-by: Alexey Charkov <alchark@gmail.com>
> ---
> .../boot/dts/rockchip/rk3576-armsom-sige5.dts | 28 ++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3576-armsom-sige5.dts b/arch/arm64/boot/dts/rockchip/rk3576-armsom-sige5.dts
> index b09e789c75c47fec7cf7e9810ab0dcca32d9404a..d9c129be55a0d997e04e6d677cdc98fb50353418 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3576-armsom-sige5.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3576-armsom-sige5.dts
> @@ -207,6 +207,22 @@ vcc_3v3_ufs_s0: regulator-vcc-ufs-s0 {
> };
> };
>
> +&cpu_b0 {
> + cpu-supply = <&vdd_cpu_big_s0>;
> +};
> +
> +&cpu_b1 {
> + cpu-supply = <&vdd_cpu_big_s0>;
> +};
> +
> +&cpu_b2 {
> + cpu-supply = <&vdd_cpu_big_s0>;
> +};
> +
> +&cpu_b3 {
> + cpu-supply = <&vdd_cpu_big_s0>;
> +};
> +
> &combphy0_ps {
> status = "okay";
> };
> @@ -215,6 +231,18 @@ &cpu_l0 {
> cpu-supply = <&vdd_cpu_lit_s0>;
> };
>
> +&cpu_l1 {
> + cpu-supply = <&vdd_cpu_lit_s0>;
> +};
> +
> +&cpu_l2 {
> + cpu-supply = <&vdd_cpu_lit_s0>;
> +};
> +
> +&cpu_l3 {
> + cpu-supply = <&vdd_cpu_lit_s0>;
> +};
> +
> &gmac0 {
> phy-mode = "rgmii-id";
> clock_in_out = "output";
>
>
Reviewed-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Tested-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
> so that cpufreq can pick them up.
Fwiw, even without this patch they're picked up by cpufreq-dt for me:
user@trixie:~$ sudo cpupower frequency-info
analyzing CPU 5:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 4 5 6 7
CPUs which need to have their frequency coordinated by software: 4 5 6 7
maximum transition latency: 40.0 us
hardware limits: 408 MHz - 2.30 GHz
available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.30 GHz
available cpufreq governors: ondemand userspace performance schedutil
current policy: frequency should be within 408 MHz and 2.30 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: 1.61 GHz (asserted by call to hardware)
user@trixie:~$ uname -a
Linux trixie 6.15.0-11173-g546b1c9e93c2 #2 SMP PREEMPT Wed Jun 4 20:32:52 CEST 2025 aarch64 GNU/Linux
this is more correct though of course.
Kind regards,
Nicolas Frattaroli
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Alexey Charkov <alchark@gmail.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Alexey Charkov <alchark@gmail.com>
Subject: Re: [PATCH 1/4] arm64: dts: rockchip: list all CPU supplies on ArmSoM Sige5
Date: Wed, 04 Jun 2025 20:38:03 +0200 [thread overview]
Message-ID: <6656934.DvuYhMxLoT@workhorse> (raw)
In-Reply-To: <20250603-sige5-updates-v1-1-717e8ce4ab77@gmail.com>
On Tuesday, 3 June 2025 19:01:13 Central European Summer Time Alexey Charkov wrote:
> List both CPU supply regulators which drive the little and big CPU
> clusters, respectively, so that cpufreq can pick them up.
>
> Signed-off-by: Alexey Charkov <alchark@gmail.com>
> ---
> .../boot/dts/rockchip/rk3576-armsom-sige5.dts | 28 ++++++++++++++++++++++
> 1 file changed, 28 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3576-armsom-sige5.dts b/arch/arm64/boot/dts/rockchip/rk3576-armsom-sige5.dts
> index b09e789c75c47fec7cf7e9810ab0dcca32d9404a..d9c129be55a0d997e04e6d677cdc98fb50353418 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3576-armsom-sige5.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3576-armsom-sige5.dts
> @@ -207,6 +207,22 @@ vcc_3v3_ufs_s0: regulator-vcc-ufs-s0 {
> };
> };
>
> +&cpu_b0 {
> + cpu-supply = <&vdd_cpu_big_s0>;
> +};
> +
> +&cpu_b1 {
> + cpu-supply = <&vdd_cpu_big_s0>;
> +};
> +
> +&cpu_b2 {
> + cpu-supply = <&vdd_cpu_big_s0>;
> +};
> +
> +&cpu_b3 {
> + cpu-supply = <&vdd_cpu_big_s0>;
> +};
> +
> &combphy0_ps {
> status = "okay";
> };
> @@ -215,6 +231,18 @@ &cpu_l0 {
> cpu-supply = <&vdd_cpu_lit_s0>;
> };
>
> +&cpu_l1 {
> + cpu-supply = <&vdd_cpu_lit_s0>;
> +};
> +
> +&cpu_l2 {
> + cpu-supply = <&vdd_cpu_lit_s0>;
> +};
> +
> +&cpu_l3 {
> + cpu-supply = <&vdd_cpu_lit_s0>;
> +};
> +
> &gmac0 {
> phy-mode = "rgmii-id";
> clock_in_out = "output";
>
>
Reviewed-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Tested-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
> so that cpufreq can pick them up.
Fwiw, even without this patch they're picked up by cpufreq-dt for me:
user@trixie:~$ sudo cpupower frequency-info
analyzing CPU 5:
driver: cpufreq-dt
CPUs which run at the same hardware frequency: 4 5 6 7
CPUs which need to have their frequency coordinated by software: 4 5 6 7
maximum transition latency: 40.0 us
hardware limits: 408 MHz - 2.30 GHz
available frequency steps: 408 MHz, 600 MHz, 816 MHz, 1.01 GHz, 1.20 GHz, 1.42 GHz, 1.61 GHz, 1.80 GHz, 2.02 GHz, 2.21 GHz, 2.30 GHz
available cpufreq governors: ondemand userspace performance schedutil
current policy: frequency should be within 408 MHz and 2.30 GHz.
The governor "schedutil" may decide which speed to use
within this range.
current CPU frequency: 1.61 GHz (asserted by call to hardware)
user@trixie:~$ uname -a
Linux trixie 6.15.0-11173-g546b1c9e93c2 #2 SMP PREEMPT Wed Jun 4 20:32:52 CEST 2025 aarch64 GNU/Linux
this is more correct though of course.
Kind regards,
Nicolas Frattaroli
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-06-04 19:43 UTC|newest]
Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 17:01 [PATCH 0/4] arm64: dts: rockchip: enable further peripherals on ArmSoM Sige5 Alexey Charkov
2025-06-03 17:01 ` Alexey Charkov
2025-06-03 17:01 ` [PATCH 1/4] arm64: dts: rockchip: list all CPU supplies " Alexey Charkov
2025-06-03 17:01 ` Alexey Charkov
2025-06-04 18:38 ` Nicolas Frattaroli [this message]
2025-06-04 18:38 ` Nicolas Frattaroli
2025-06-04 19:12 ` Alexey Charkov
2025-06-04 19:12 ` Alexey Charkov
2025-06-04 19:23 ` Nicolas Frattaroli
2025-06-04 19:23 ` Nicolas Frattaroli
2025-06-04 19:54 ` Alexey Charkov
2025-06-04 19:54 ` Alexey Charkov
2025-06-05 13:22 ` Piotr Oniszczuk
2025-06-05 13:22 ` Piotr Oniszczuk
2025-06-05 13:42 ` Alexey Charkov
2025-06-05 13:42 ` Alexey Charkov
2025-06-08 7:24 ` Piotr Oniszczuk
2025-06-08 7:24 ` Piotr Oniszczuk
2025-06-09 14:05 ` Alexey Charkov
2025-06-09 14:05 ` Alexey Charkov
2025-06-15 15:59 ` Piotr Oniszczuk
2025-06-15 15:59 ` Piotr Oniszczuk
2025-06-15 16:20 ` Alexey Charkov
2025-06-15 16:20 ` Alexey Charkov
2025-06-18 13:51 ` Alexey Charkov
2025-06-18 13:51 ` Alexey Charkov
2025-06-18 14:06 ` Nicolas Frattaroli
2025-06-18 14:06 ` Nicolas Frattaroli
2025-06-18 14:48 ` Alexey Charkov
2025-06-18 14:48 ` Alexey Charkov
2025-06-20 16:02 ` Alexey Charkov
2025-06-20 16:02 ` Alexey Charkov
2025-06-21 19:35 ` Alexey Charkov
2025-06-21 19:35 ` Alexey Charkov
2025-06-21 19:44 ` Heiko Stuebner
2025-06-21 19:44 ` Heiko Stuebner
2025-06-21 21:21 ` Alexey Charkov
2025-06-21 21:21 ` Alexey Charkov
2025-06-22 13:48 ` Heiko Stuebner
2025-06-22 13:48 ` Heiko Stuebner
2025-06-23 9:19 ` Alexey Charkov
2025-06-23 9:19 ` Alexey Charkov
2025-06-23 13:58 ` Alexey Charkov
2025-06-23 13:58 ` Alexey Charkov
2025-06-23 15:02 ` Piotr Oniszczuk
2025-06-23 15:02 ` Piotr Oniszczuk
2025-06-23 17:40 ` Jonas Karlman
2025-06-23 17:40 ` Jonas Karlman
2025-06-23 21:07 ` Jonas Karlman
2025-06-23 21:07 ` Jonas Karlman
2025-06-23 21:17 ` Heiko Stuebner
2025-06-23 21:17 ` Heiko Stuebner
2025-06-24 7:41 ` Alexey Charkov
2025-06-24 7:41 ` Alexey Charkov
2025-06-23 18:04 ` Jonas Karlman
2025-06-23 18:04 ` Jonas Karlman
2025-06-05 11:17 ` Diederik de Haas
2025-06-05 11:17 ` Diederik de Haas
2025-06-05 11:23 ` Alexey Charkov
2025-06-05 11:23 ` Alexey Charkov
2025-06-03 17:01 ` [PATCH 2/4] arm64: dts: rockchip: enable USB A ports " Alexey Charkov
2025-06-03 17:01 ` Alexey Charkov
2025-06-03 17:51 ` Nicolas Frattaroli
2025-06-03 17:51 ` Nicolas Frattaroli
2025-06-04 6:52 ` Alexey Charkov
2025-06-04 6:52 ` Alexey Charkov
2025-06-04 13:24 ` Nicolas Frattaroli
2025-06-04 13:24 ` Nicolas Frattaroli
2025-06-03 17:01 ` [PATCH 3/4] arm64: dts: rockchip: enable wifi " Alexey Charkov
2025-06-03 17:01 ` Alexey Charkov
2025-06-04 19:01 ` Nicolas Frattaroli
2025-06-04 19:01 ` Nicolas Frattaroli
2025-06-04 19:48 ` Alexey Charkov
2025-06-04 19:48 ` Alexey Charkov
2025-06-05 2:43 ` Jimmy Hon
2025-06-05 2:43 ` Jimmy Hon
2025-06-05 6:32 ` Alexey Charkov
2025-06-05 6:32 ` Alexey Charkov
2025-06-05 14:14 ` Alexey Charkov
2025-06-05 14:14 ` Alexey Charkov
2025-06-07 2:42 ` Jimmy Hon
2025-06-07 2:42 ` Jimmy Hon
2025-06-03 17:01 ` [PATCH 4/4] arm64: dts: rockchip: enable bluetooth " Alexey Charkov
2025-06-03 17:01 ` Alexey Charkov
2025-06-04 13:58 ` [PATCH 0/4] arm64: dts: rockchip: enable further peripherals " Rob Herring (Arm)
2025-06-04 13:58 ` Rob Herring (Arm)
2025-06-04 14:15 ` Alexey Charkov
2025-06-04 14:15 ` Alexey Charkov
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=6656934.DvuYhMxLoT@workhorse \
--to=nicolas.frattaroli@collabora.com \
--cc=alchark@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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 \
/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.