From: Heiko Stuebner <heiko@sntech.de>
To: Diederik de Haas <diederik@cknow-tech.com>
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
michael.riesch@collabora.com
Subject: Re: [PATCH 2/3] arm64: dts: rockchip: use SCMI clock id for cpu clock on rk356x
Date: Thu, 06 Nov 2025 00:43:26 +0100 [thread overview]
Message-ID: <5996423.DvuYhMxLoT@phil> (raw)
In-Reply-To: <DE0SFV203UMS.1ZV2JE6QEPN29@cknow-tech.com>
Am Mittwoch, 5. November 2025, 14:16:42 Mitteleuropäische Normalzeit schrieb Diederik de Haas:
> Hi Heiko,
>
> On Tue Nov 4, 2025 at 12:49 AM CET, Heiko Stuebner wrote:
> > Instead of hard-coding 0, use the more descriptive ID from the binding
> > to reference the SCMI clock for the cpu on rk356x.
>
> Any particular reason you only did it for the cpu, but not the gpu?
Didn't think of if at the time :-) .
Will prepare another one for the GPU.
Heiko
>
> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > ---
> > arch/arm64/boot/dts/rockchip/rk356x-base.dtsi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> > index a3361527d4fe..d0c76401b45e 100644
> > --- a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> > +++ b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> > @@ -53,7 +53,7 @@ cpu0: cpu@0 {
> > device_type = "cpu";
> > compatible = "arm,cortex-a55";
> > reg = <0x0 0x0>;
> > - clocks = <&scmi_clk 0>;
> > + clocks = <&scmi_clk SCMI_CLK_CPU>;
>
> Regardless of the above comment, feel free to add
>
> Reviewed-by: Diederik de Haas <diederik@cknow-tech.com>
>
> Cheers,
> Diederik
>
> > #cooling-cells = <2>;
> > enable-method = "psci";
> > i-cache-size = <0x8000>;
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Heiko Stuebner <heiko@sntech.de>
To: Diederik de Haas <diederik@cknow-tech.com>
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
michael.riesch@collabora.com
Subject: Re: [PATCH 2/3] arm64: dts: rockchip: use SCMI clock id for cpu clock on rk356x
Date: Thu, 06 Nov 2025 00:43:26 +0100 [thread overview]
Message-ID: <5996423.DvuYhMxLoT@phil> (raw)
In-Reply-To: <DE0SFV203UMS.1ZV2JE6QEPN29@cknow-tech.com>
Am Mittwoch, 5. November 2025, 14:16:42 Mitteleuropäische Normalzeit schrieb Diederik de Haas:
> Hi Heiko,
>
> On Tue Nov 4, 2025 at 12:49 AM CET, Heiko Stuebner wrote:
> > Instead of hard-coding 0, use the more descriptive ID from the binding
> > to reference the SCMI clock for the cpu on rk356x.
>
> Any particular reason you only did it for the cpu, but not the gpu?
Didn't think of if at the time :-) .
Will prepare another one for the GPU.
Heiko
>
> > Signed-off-by: Heiko Stuebner <heiko@sntech.de>
> > ---
> > arch/arm64/boot/dts/rockchip/rk356x-base.dtsi | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> > index a3361527d4fe..d0c76401b45e 100644
> > --- a/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> > +++ b/arch/arm64/boot/dts/rockchip/rk356x-base.dtsi
> > @@ -53,7 +53,7 @@ cpu0: cpu@0 {
> > device_type = "cpu";
> > compatible = "arm,cortex-a55";
> > reg = <0x0 0x0>;
> > - clocks = <&scmi_clk 0>;
> > + clocks = <&scmi_clk SCMI_CLK_CPU>;
>
> Regardless of the above comment, feel free to add
>
> Reviewed-by: Diederik de Haas <diederik@cknow-tech.com>
>
> Cheers,
> Diederik
>
> > #cooling-cells = <2>;
> > enable-method = "psci";
> > i-cache-size = <0x8000>;
>
>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-11-05 23:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 23:49 [PATCH 0/3] SCMI clocks on RK356x Heiko Stuebner
2025-11-03 23:49 ` Heiko Stuebner
2025-11-03 23:49 ` [PATCH 1/3] dt-bindings: clock: rk3568: Add SCMI clock ids Heiko Stuebner
2025-11-03 23:49 ` Heiko Stuebner
2025-11-04 17:25 ` Conor Dooley
2025-11-04 17:25 ` Conor Dooley
2025-11-05 13:08 ` Diederik de Haas
2025-11-05 13:08 ` Diederik de Haas
2025-11-03 23:49 ` [PATCH 2/3] arm64: dts: rockchip: use SCMI clock id for cpu clock on rk356x Heiko Stuebner
2025-11-03 23:49 ` Heiko Stuebner
2025-11-05 13:16 ` Diederik de Haas
2025-11-05 13:16 ` Diederik de Haas
2025-11-05 23:43 ` Heiko Stuebner [this message]
2025-11-05 23:43 ` Heiko Stuebner
2025-11-03 23:49 ` [PATCH 3/3] arm64: dts: rockchip: add missing clocks for cpu cores " Heiko Stuebner
2025-11-03 23:49 ` Heiko Stuebner
2025-11-05 13:18 ` Diederik de Haas
2025-11-05 13:18 ` Diederik de Haas
2025-11-05 23:26 ` [PATCH 0/3] SCMI clocks on RK356x Heiko Stuebner
2025-11-05 23:26 ` Heiko Stuebner
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=5996423.DvuYhMxLoT@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=diederik@cknow-tech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@collabora.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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.