From: Kendall Willis <k-willis@ti.com>
To: Dhruva Gole <d-gole@ti.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Nishanth Menon <nm@ti.com>,
"Vignesh Raghavendra" <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Sebin Francis <sebin.francis@ti.com>, Bryan Brattlof <bb@ti.com>,
<linux-pm@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] arm64: dts: ti: k3-am62l: support cpufreq
Date: Wed, 21 Jan 2026 10:27:15 -0600 [thread overview]
Message-ID: <652d6b5a-57cc-4985-87fb-94eb53c520be@ti.com> (raw)
In-Reply-To: <20260120-am62l-cpufreq-v3-3-8c69b80168a3@ti.com>
On 1/20/26 05:47, Dhruva Gole wrote:
> Enable CPUFreq support for AM62L SoC by adding the relevant OPP efuse table
> syscon to k3-am62l-wakeup.dtsi for speed grade detection.
>
> Add the operating-points-v2 table with CPU frequency steps from 200MHz to
> 1.25GHz to k3-am62l3.dtsi
>
> Configure CPU clocks to reference the SCMI clock controller for frequency
> scaling
>
> This enables proper CPU frequency scaling capabilities for the AM62L SoC
> using the ARM SCMI protocol to interact with the power management firmware.
>
> Signed-off-by: Dhruva Gole <d-gole@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi | 5 +++
> arch/arm64/boot/dts/ti/k3-am62l3.dtsi | 47 +++++++++++++++++++++++++++++
> 2 files changed, 52 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi b/arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi
> index 61bfcdcfc66ea8d802a36ed43cd01fbbf3decc70..a42ccd0d2fcc4d204cae81508f839c44ce83f558 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62l-wakeup.dtsi
> @@ -127,6 +127,11 @@ chipid: chipid@14 {
> bootph-all;
> };
>
> + opp_efuse_table: syscon@18 {
> + compatible = "ti,am62-opp-efuse-table", "syscon";
> + reg = <0x18 0x4>;
> + };
> +
> cpsw_mac_syscon: ethernet-mac-syscon@2000 {
> compatible = "ti,am62p-cpsw-mac-efuse", "syscon";
> reg = <0x2000 0x8>;
> diff --git a/arch/arm64/boot/dts/ti/k3-am62l3.dtsi b/arch/arm64/boot/dts/ti/k3-am62l3.dtsi
> index da220b85151227c63f59b2b8ec48ae2ebb37e7bf..f7146421918f7037c6a192cc4765e8814a508afc 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62l3.dtsi
> +++ b/arch/arm64/boot/dts/ti/k3-am62l3.dtsi
> @@ -39,6 +39,8 @@ cpu0: cpu@0 {
> d-cache-line-size = <64>;
> d-cache-sets = <128>;
> next-level-cache = <&l2_0>;
> + operating-points-v2 = <&a53_opp_table>;
> + clocks = <&scmi_clk 356>;
> };
>
> cpu1: cpu@1 {
> @@ -53,6 +55,8 @@ cpu1: cpu@1 {
> d-cache-line-size = <64>;
> d-cache-sets = <128>;
> next-level-cache = <&l2_0>;
> + operating-points-v2 = <&a53_opp_table>;
> + clocks = <&scmi_clk 356>;
> };
> };
>
> @@ -64,4 +68,47 @@ l2_0: l2-cache0 {
> cache-line-size = <64>;
> cache-sets = <256>;
> };
> +
> + a53_opp_table: opp-table {
> + compatible = "operating-points-v2-ti-cpu";
> + opp-shared;
> + syscon = <&opp_efuse_table>;
> +
> + opp-200000000 {
> + opp-hz = /bits/ 64 <200000000>;
> + opp-supported-hw = <0x01 0x0007>;
> + clock-latency-ns = <6000000>;
> + };
> +
> + opp-400000000 {
> + opp-hz = /bits/ 64 <400000000>;
> + opp-supported-hw = <0x01 0x0007>;
> + clock-latency-ns = <6000000>;
> + };
> +
> + opp-600000000 {
> + opp-hz = /bits/ 64 <600000000>;
> + opp-supported-hw = <0x01 0x0007>;
> + clock-latency-ns = <6000000>;
> + };
> +
> + opp-800000000 {
> + opp-hz = /bits/ 64 <800000000>;
> + opp-supported-hw = <0x01 0x0007>;
> + clock-latency-ns = <6000000>;
> + };
> +
> + opp-1000000000 {
> + opp-hz = /bits/ 64 <1000000000>;
> + opp-supported-hw = <0x01 0x0006>;
> + clock-latency-ns = <6000000>;
> + };
> +
> + opp-1250000000 {
> + opp-hz = /bits/ 64 <1250000000>;
> + opp-supported-hw = <0x01 0x0003>;
What is determining the opp-supported-hw values? To my understanding
based on the DT bindings docs, the values should be based on the number
of unique speed grades, which there are two for AM62L. Looking at the
values used here, it looks like it shows 3 unique speed grades.
By this logic, the value of opp-supported-hw should be something like
0x03 for all OPPs below 833 MHz and 0x02 for all values above it.
> + clock-latency-ns = <6000000>;
> + opp-suspend;
> + };
> + };
> };
>
Best,
Kendall Willis <k-willis@ti.com>
next prev parent reply other threads:[~2026-01-21 16:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 11:47 [PATCH v3 0/3] cpufreq: ti: Add support for AM62L3 SoC Dhruva Gole
2026-01-20 11:47 ` [PATCH v3 1/3] cpufreq: dt-platdev: Add ti,am62l3 to blocklist Dhruva Gole
2026-01-20 11:47 ` [PATCH v3 2/3] cpufreq: ti-cpufreq: add support for AM62L3 SoC Dhruva Gole
2026-01-20 23:09 ` Kendall Willis
2026-01-20 11:47 ` [PATCH v3 3/3] arm64: dts: ti: k3-am62l: support cpufreq Dhruva Gole
2026-01-21 16:27 ` Kendall Willis [this message]
2026-01-22 10:36 ` Dhruva Gole
2026-01-21 6:28 ` [PATCH v3 0/3] cpufreq: ti: Add support for AM62L3 SoC Viresh Kumar
2026-01-21 6:38 ` Dhruva Gole
2026-01-21 7:07 ` Viresh Kumar
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=652d6b5a-57cc-4985-87fb-94eb53c520be@ti.com \
--to=k-willis@ti.com \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=sebin.francis@ti.com \
--cc=vigneshr@ti.com \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®