From: Ryan Walklin <ryan@testtoast.com>
To: 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>,
Andre Przywara <andre.przywara@arm.com>
Cc: 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>,
Ryan Walklin <ryan@testtoast.com>
Subject: [PATCH 0/3] cpufreq: sun50i: add Allwinner H700 speed bin and additional OPPs
Date: Fri, 7 Jun 2024 21:20:32 +1200 [thread overview]
Message-ID: <20240607092140.33112-1-ryan@testtoast.com> (raw)
Hi,
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 and in use in vendor BSPs were found to be unstable during testing, so the H700 speed bin was not included in the mainline driver.
Retesting with kernel 6.10rc2 (which carries subsequent fixes for the driver) shows stable operation with these additional OPPs.
This patchset adds the H700 speedbin index, enables the additional operating points for the H700 in the H616 OPP table, and enables DVFS support for the Anbernic REG35XX handheld devices, which are the only mainline-supported devices currently using the H700.
Regards,
Ryan
[1] https://lore.kernel.org/linux-sunxi/20240418154408.1740047-1-andre.przywara@arm.com
Ryan Walklin (3):
cpufreq: sun50i: add Allwinner H700 speed bin
arm64: dts: allwinner: h616: add additional CPU OPPs for the H700
arm64: dts: allwinner: rg35xx: Enable DVFS CPU frequency scaling
.../dts/allwinner/sun50i-h616-cpu-opp.dtsi | 25 +++++++++++++------
.../sun50i-h700-anbernic-rg35xx-2024.dts | 4 +--
drivers/cpufreq/sun50i-cpufreq-nvmem.c | 3 +++
3 files changed, 23 insertions(+), 9 deletions(-)
--
2.45.2
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2024-06-07 9:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 9:20 Ryan Walklin [this message]
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
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=20240607092140.33112-1-ryan@testtoast.com \
--to=ryan@testtoast.com \
--cc=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=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).