From: Andre Przywara <andre.przywara@arm.com>
To: Ryan Walklin <ryan@testtoast.com>
Cc: Yangtao Li <tiny.windzz@gmail.com>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Viresh Kumar <vireshk@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Samuel Holland <samuel@sholland.org>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev,
Chris Morgan <macroalpha82@gmail.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH 2/3] arm64: dts: allwinner: h616: add additional CPU OPPs for the H700
Date: Wed, 19 Jun 2024 01:00:35 +0100 [thread overview]
Message-ID: <20240619010035.7aa1bd04@minigeek.lan> (raw)
In-Reply-To: <20240607092140.33112-3-ryan@testtoast.com>
On Fri, 7 Jun 2024 21:20:34 +1200
Ryan Walklin <ryan@testtoast.com> wrote:
Hi,
> The H700 now shows stable operation with the 1.008, 1.032 and 1.512 GHz
> DVFS operating points. The 1.5GHz OPP requires a VDD-CPU of 1.16V,
> obtained from the vendor BSP. This voltage is slightly above the
> recommended operating voltage for the H616 (H700 datasheet not publicly
> available) but well within the absolute maximum of 1.3V.
>
> Add the additional 1.032 GHz operating point to the H616 CPU-OPP table,
> and enable the 1.008 and 1.512 points for the H700.
This matches the values I had in the previous version of this patch:
> Signed-off-by: Ryan Walklin <ryan@testtoast.com>
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Cheers,
Andre
> ---
> .../dts/allwinner/sun50i-h616-cpu-opp.dtsi | 25 +++++++++++++------
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/allwinner/sun50i-h616-cpu-opp.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-h616-cpu-opp.dtsi
> index aca22a7f0191c..dd10aaf472b66 100644
> --- a/arch/arm64/boot/dts/allwinner/sun50i-h616-cpu-opp.dtsi
> +++ b/arch/arm64/boot/dts/allwinner/sun50i-h616-cpu-opp.dtsi
> @@ -11,7 +11,7 @@ opp-480000000 {
> opp-hz = /bits/ 64 <480000000>;
> opp-microvolt = <900000>;
> clock-latency-ns = <244144>; /* 8 32k periods */
> - opp-supported-hw = <0x1f>;
> + opp-supported-hw = <0x3f>;
> };
>
> opp-600000000 {
> @@ -25,7 +25,7 @@ opp-720000000 {
> opp-hz = /bits/ 64 <720000000>;
> opp-microvolt = <900000>;
> clock-latency-ns = <244144>; /* 8 32k periods */
> - opp-supported-hw = <0x0d>;
> + opp-supported-hw = <0x2d>;
> };
>
> opp-792000000 {
> @@ -50,8 +50,16 @@ opp-1008000000 {
> opp-microvolt-speed2 = <950000>;
> opp-microvolt-speed3 = <950000>;
> opp-microvolt-speed4 = <1020000>;
> + opp-microvolt-speed5 = <900000>;
> clock-latency-ns = <244144>; /* 8 32k periods */
> - opp-supported-hw = <0x1f>;
> + opp-supported-hw = <0x3f>;
> + };
> +
> + opp-1032000000 {
> + opp-hz = /bits/ 64 <1032000000>;
> + opp-microvolt = <900000>;
> + clock-latency-ns = <244144>; /* 8 32k periods */
> + opp-supported-hw = <0x20>;
> };
>
> opp-1104000000 {
> @@ -59,8 +67,9 @@ opp-1104000000 {
> opp-microvolt-speed0 = <1000000>;
> opp-microvolt-speed2 = <1000000>;
> opp-microvolt-speed3 = <1000000>;
> + opp-microvolt-speed5 = <950000>;
> clock-latency-ns = <244144>; /* 8 32k periods */
> - opp-supported-hw = <0x0d>;
> + opp-supported-hw = <0x2d>;
> };
>
> opp-1200000000 {
> @@ -70,8 +79,9 @@ opp-1200000000 {
> opp-microvolt-speed2 = <1050000>;
> opp-microvolt-speed3 = <1050000>;
> opp-microvolt-speed4 = <1100000>;
> + opp-microvolt-speed5 = <1020000>;
> clock-latency-ns = <244144>; /* 8 32k periods */
> - opp-supported-hw = <0x1f>;
> + opp-supported-hw = <0x3f>;
> };
>
> opp-1320000000 {
> @@ -85,15 +95,16 @@ opp-1416000000 {
> opp-hz = /bits/ 64 <1416000000>;
> opp-microvolt = <1100000>;
> clock-latency-ns = <244144>; /* 8 32k periods */
> - opp-supported-hw = <0x0d>;
> + opp-supported-hw = <0x2d>;
> };
>
> opp-1512000000 {
> opp-hz = /bits/ 64 <1512000000>;
> opp-microvolt-speed1 = <1100000>;
> opp-microvolt-speed3 = <1100000>;
> + opp-microvolt-speed5 = <1160000>;
> clock-latency-ns = <244144>; /* 8 32k periods */
> - opp-supported-hw = <0x0a>;
> + opp-supported-hw = <0x2a>;
> };
> };
> };
next prev parent reply other threads:[~2024-06-19 0:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 9:20 [PATCH 0/3] cpufreq: sun50i: add Allwinner H700 speed bin and additional OPPs Ryan Walklin
2024-06-07 9:20 ` [PATCH 1/3] cpufreq: sun50i: add Allwinner H700 speed bin Ryan Walklin
2024-06-19 0:00 ` Andre Przywara
2024-06-19 3:16 ` Viresh Kumar
2024-06-07 9:20 ` [PATCH 2/3] arm64: dts: allwinner: h616: add additional CPU OPPs for the H700 Ryan Walklin
2024-06-19 0:00 ` Andre Przywara [this message]
2024-06-07 9:20 ` [PATCH 3/3] arm64: dts: allwinner: rg35xx: Enable DVFS CPU frequency scaling Ryan Walklin
2024-06-19 0:00 ` Andre Przywara
2024-06-22 15:17 ` (subset) [PATCH 0/3] cpufreq: sun50i: add Allwinner H700 speed bin and additional OPPs Chen-Yu Tsai
2024-06-25 15:21 ` Philippe Simons
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=20240619010035.7aa1bd04@minigeek.lan \
--to=andre.przywara@arm.com \
--cc=conor+dt@kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=macroalpha82@gmail.com \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=ryan@testtoast.com \
--cc=samuel@sholland.org \
--cc=sboyd@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tiny.windzz@gmail.com \
--cc=vireshk@kernel.org \
--cc=wens@csie.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;
as well as URLs for NNTP newsgroup(s).