From: "Christain Stefan Köver-Draxl" <ckoever@outlook.de>
To: Chuan Liu <chuan.liu@amlogic.com>
Cc: neil.armstrong@linaro.org, conor+dt@kernel.org,
linux-clk@vger.kernel.org, rafael@kernel.org, sboyd@kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
chuan.liu@amlogic.com, martin.blumenstingl@googlemail.com,
devicetree@vger.kernel.org, khilman@baylibre.com,
linux-amlogic@lists.infradead.org, krzk+dt@kernel.org,
bmasney+clk@redhat.com, robh@kernel.org,
linux-arm-kernel@lists.infradead.org,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [PATCH 4/4] cpufreq: add an Amlogic speed-bin driver
Date: Fri, 6 Nov 2026 09:56:47 +0100 [thread overview]
Message-ID: <MMZPR08MB549315BEDE7233BD6C86F70EC8DF762@MMZPR08MB549315.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <4a51e879-708c-49dc-a08a-3f64eeec8bbf@amlogic.com>
On 10/29/26 13:29, Chuan Liu wrote:
> We have done a lot of optimization on these issues from both the
> hardware and software sides, and we would like the cpufreq driver we
> submit upstream to cover these optimizations as much as possible.
Hi Chuan,
thank you for the explanations. I will not resend the S4 cpufreq series
and wait for your patches instead. I can test it on my S905W2 board when
you post it.
On the regulator settling time: on this board I have not seen hangs with
the vendor OPP table since the PWM clocks stopped running from vid_pll,
but I have no ramp delay set, so Christian's regulator-ramp-delay is
very likely what made his transitions stable, and I would rely on that too.
Best regards,
Christian K.-D.
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-11-06 8:57 UTC|newest]
Thread overview: 21+ 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
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-13 14:32 ` Jerome Brunet
2026-11-06 8:56 ` Christain Stefan Köver-Draxl [this message]
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=MMZPR08MB549315BEDE7233BD6C86F70EC8DF762@MMZPR08MB549315.eurprd08.prod.outlook.com \
--to=ckoever@outlook.de \
--cc=bmasney+clk@redhat.com \
--cc=chuan.liu@amlogic.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 \
--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®