From: Kendall Willis <k-willis@ti.com>
To: Dhruva Gole <d-gole@ti.com>, 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: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Bryan Brattlof <bb@ti.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: Re: [PATCH] arm64: dts: ti: k3-am62l: support cpufreq
Date: Thu, 22 Jan 2026 10:17:37 -0600 [thread overview]
Message-ID: <1878d1e8-df99-445e-82d9-1a76c934fda1@ti.com> (raw)
In-Reply-To: <77b3b869-558f-4854-95b0-57980be28032@ti.com>
On 1/22/26 10:14, Kendall Willis wrote:
> On 1/22/26 04:49, 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>
>
> Reviewed-by: Kendall Willis <k-willis@ti.com>
>
> Best,
> Kendall Willis <k-willis@ti.com>
Oops sent my reviewed by on the wrong revision.
Best,
Kendall Willis
prev parent reply other threads:[~2026-01-22 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-22 10:49 Dhruva Gole
2026-01-22 11:26 ` Viresh Kumar
2026-01-22 15:44 ` Dhruva Gole
2026-01-22 14:36 ` Kendall Willis
2026-01-22 15:45 ` Dhruva Gole
2026-01-22 16:14 ` Kendall Willis
2026-01-22 16:17 ` Kendall Willis [this message]
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=1878d1e8-df99-445e-82d9-1a76c934fda1@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=nm@ti.com \
--cc=robh@kernel.org \
--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®