From: "Christain Stefan Köver-Draxl" <ckoever@outlook.de>
To: Jerome Brunet <jbrunet@baylibre.com>
Cc: neil.armstrong@linaro.org, sboyd@kernel.org,
bmasney+clk@redhat.com, khilman@baylibre.com,
martin.blumenstingl@googlemail.com, rafael@kernel.org,
robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
"Christian Stefan Kövér-Draxl" <ckoever@outlook.de>
Subject: Re: [PATCH 4/4] cpufreq: add an Amlogic speed-bin driver
Date: Mon, 26 Oct 2026 11:08:04 +0100 [thread overview]
Message-ID: <MMZPR08MB549315DB32DCE8589A27E461B5DF612@MMZPR08MB549315.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <at8WfX_G0tfTlFrm@vireshk-B250M-D3H>
Hi Viresh,
Hi Jerome,
On 10/26/26 09:59, Viresh Kumar wrote:
> On 26-10-26, 09:57, Jerome Brunet wrote:
>> On lun. 26 oct. 2026 at 11:00, Viresh Kumar <viresh.kumar@linaro.org> wrote:
>>
>>> On 25-10-26, 20:22, christian.koever-draxl@student.uibk.ac.at wrote:
>>>> From: Christian Stefan Kövér-Draxl <ckoever@outlook.de>
>>>>
>>>> Every S4 speed bin runs the same CPU frequencies but needs its own
>>>> voltage curve, and the bin can only be read through the secure monitor.
>>>>
>>>> Read the bin from the firmware, select the matching
>>>> "opp-microvolt-speed<bin>" property for all CPUs, then register
>>>> cpufreq-dt. Bins outside the known range fall back to bin 0, which
>>>> has the highest voltages. Like sun50i-cpufreq-nvmem, the driver binds
>>>> on the SoC compatible and needs no node of its own, and S4 is added to
>>>> the cpufreq-dt-platdev blocklist so cpufreq-dt is only created after
>>>> the bin has been applied.
>>>>
>>>> Signed-off-by: Christian Stefan Kövér-Draxl <ckoever@outlook.de>
>>>> ---
>>>> MAINTAINERS | 1 +
>>>> drivers/cpufreq/Kconfig.arm | 14 ++
>>>> drivers/cpufreq/Makefile | 1 +
>>>> drivers/cpufreq/amlogic-cpufreq.c | 184 +++++++++++++++++++++++++++
>>>> drivers/cpufreq/cpufreq-dt-platdev.c | 2 +
>>>> 5 files changed, 202 insertions(+)
>>>> create mode 100644 drivers/cpufreq/amlogic-cpufreq.c
>>> Is it safe to apply just this one ? I can take this via the PM tree then.
>> I would advise to wait a little for Amlogic to chime in.
Viresh, thanks, but please don't apply it alone. It would need the
speed-bin call from patch 3 (meson_sm), and without the CPU clock from
patch 2 it has nothing to scale.
Best regards,
Christian
> Sure, I wasn't going to wait for the maintainers to respond anyway.
>
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-10-26 10:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 19:22 [PATCH 0/4] arm64: amlogic: S4 CPU frequency scaling christian.koever-draxl
2026-10-25 19:22 ` [PATCH 1/4] dt-bindings: clock: amlogic,s4-pll-clkc: add the CPU clock christian.koever-draxl
2026-10-30 11:15 ` Krzysztof Kozlowski
2026-10-25 19:22 ` [PATCH 2/4] clk: meson: s4-pll: " christian.koever-draxl
2026-10-25 19:22 ` [PATCH 3/4] firmware: meson: sm: add the CPU speed bin call christian.koever-draxl
2026-10-25 19:22 ` [PATCH 4/4] cpufreq: add an Amlogic speed-bin driver christian.koever-draxl
2026-10-26 5:30 ` Viresh Kumar
2026-10-26 8:57 ` Jerome Brunet
2026-10-26 8:59 ` Viresh Kumar
2026-10-26 10:08 ` Christain Stefan Köver-Draxl [this message]
2026-10-27 9:26 ` Chuan Liu
2026-10-27 10:22 ` Christian Hewitt
2026-10-29 5:29 ` Chuan Liu
2026-11-01 22:51 ` Martin Blumenstingl
2026-11-03 9:45 ` Chuan Liu
2026-11-08 21:45 ` Martin Blumenstingl
2026-11-09 8:44 ` neil.armstrong
2026-11-06 8:56 ` Christain Stefan Köver-Draxl
2026-10-26 10:10 ` Christain Stefan Köver-Draxl
2026-10-27 9:31 ` Chuan Liu
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=MMZPR08MB549315DB32DCE8589A27E461B5DF612@MMZPR08MB549315.eurprd08.prod.outlook.com \
--to=ckoever@outlook.de \
--cc=bmasney+clk@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=rafael@kernel.org \
--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 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®