From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dhruva Gole <d-gole@ti.com>
Cc: "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>,
Kendall Willis <k-willis@ti.com>,
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 1/3] cpufreq: dt-platdev: Add ti,am62l3 to blocklist
Date: Fri, 16 Jan 2026 11:22:30 +0100 [thread overview]
Message-ID: <f5b8ab93-0d09-479f-9790-1072716a5de7@kernel.org> (raw)
In-Reply-To: <20260116100614.k2loytoywr4vqihu@lcpd911>
On 16/01/2026 11:06, Dhruva Gole wrote:
> On Jan 16, 2026 at 10:16:08 +0100, Krzysztof Kozlowski wrote:
>> On 16/01/2026 10:01, Dhruva Gole wrote:
>>> Add AM62L3 SoC to the dt-platdev blocklist to ensure proper handling
>>> of CPUFreq functionality. The AM62L3 will use its native TI CPUFreq
>>> driver implementation instead of the generic dt-platdev driver.
>>>
>>> This follows the same pattern as other TI SoCs like AM62A7, AM62D2,
>>> and AM62P5 which have been previously added to this blocklist.
>>>
>>> Signed-off-by: Dhruva Gole <d-gole@ti.com>
>>> ---
>>> drivers/cpufreq/cpufreq-dt-platdev.c | 1 +
>>> 1 file changed, 1 insertion(+)
>>>
>>> diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c b/drivers/cpufreq/cpufreq-dt-platdev.c
>>> index 1708179b2610bca6035d10f0f4766eee6f73912e..29122bac2e22f6e7a8e8294cc01923c8a13d53c1 100644
>>> --- a/drivers/cpufreq/cpufreq-dt-platdev.c
>>> +++ b/drivers/cpufreq/cpufreq-dt-platdev.c
>>> @@ -194,6 +194,7 @@ static const struct of_device_id blocklist[] __initconst = {
>>> { .compatible = "ti,am62a7", },
>>> { .compatible = "ti,am62d2", },
>>> { .compatible = "ti,am62p5", },
>>> + { .compatible = "ti,am62l3", },
>>
>> p > l
>
> Fair point, I thought more from a "latest SOC" point of view but the
> standard here is alphabetical, will re-spin.
This is not a TI-specific list, but all SoCs, so it is not sorted by
latest SoC. Neither sunxi nor Samsung are sorted that (I believe same
applies to others, but did not verify).
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-16 10:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-16 9:01 [PATCH 0/3] cpufreq: ti: Add support for AM62L3 SoC Dhruva Gole
2026-01-16 9:01 ` [PATCH 1/3] cpufreq: dt-platdev: Add ti,am62l3 to blocklist Dhruva Gole
2026-01-16 9:16 ` Krzysztof Kozlowski
2026-01-16 10:06 ` Dhruva Gole
2026-01-16 10:22 ` Krzysztof Kozlowski [this message]
2026-01-16 9:01 ` [PATCH 2/3] cpufreq: ti-cpufreq: add support for AM62L3 SoC Dhruva Gole
2026-01-16 9:16 ` Krzysztof Kozlowski
2026-01-16 10:08 ` Dhruva Gole
2026-01-16 9:01 ` [PATCH 3/3] arm64: dts: ti: k3-am62l: support cpufreq Dhruva Gole
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=f5b8ab93-0d09-479f-9790-1072716a5de7@kernel.org \
--to=krzk@kernel.org \
--cc=bb@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=k-willis@ti.com \
--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®