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 1/3] cpufreq: sun50i: add Allwinner H700 speed bin
Date: Wed, 19 Jun 2024 01:00:21 +0100 [thread overview]
Message-ID: <20240619010021.5962e459@minigeek.lan> (raw)
In-Reply-To: <20240607092140.33112-2-ryan@testtoast.com>
On Fri, 7 Jun 2024 21:20:33 +1200
Ryan Walklin <ryan@testtoast.com> wrote:
> Support for the Allwinner H618, H618 and H700 was added to the sun50i
> cpufreq-nvmem driver recently [1] however at the time some operating
> points supported by the H700 (1.008, 1.032 and 1.512 GHz) and in use by
> vendor BSPs were found to be unstable during testing, so the H700 speed
> bin and the 1.032 GHz OPP were not included in the mainline driver.
>
> Retesting with kernel 6.10rc2 (which carries additional fixes for the
> driver) now shows stable operation with these points.
>
> Add the H700 speed bin to the driver.
>
> Signed-off-by: Ryan Walklin <ryan@testtoast.com>
Yes, 0x6c00 is the value for the H700 SoCs in the devices we have seen:
Reviewed-by: Andre Przywara <andre.przywara@arm.com>
Thanks,
Andre
> --
> [1] https://lore.kernel.org/linux-sunxi/20240418154408.1740047-1-andre.przywara@arm.com
> ---
> drivers/cpufreq/sun50i-cpufreq-nvmem.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/cpufreq/sun50i-cpufreq-nvmem.c b/drivers/cpufreq/sun50i-cpufreq-nvmem.c
> index 0b882765cd66f..969f22aadd950 100644
> --- a/drivers/cpufreq/sun50i-cpufreq-nvmem.c
> +++ b/drivers/cpufreq/sun50i-cpufreq-nvmem.c
> @@ -91,6 +91,9 @@ static u32 sun50i_h616_efuse_xlate(u32 speedbin)
> case 0x5d00:
> value = 0;
> break;
> + case 0x6c00:
> + value = 5;
> + break;
> default:
> pr_warn("sun50i-cpufreq-nvmem: unknown speed bin 0x%x, using default bin 0\n",
> speedbin & 0xffff);
next prev parent reply other threads:[~2024-06-19 0:01 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 [this message]
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
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=20240619010021.5962e459@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