From: Alexander Sverdlin <alex@sverdlin.org>
To: rajanyadav0307@gmail.com
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Cody Eksal <masterr3c0rd@epochal.quest>
Subject: Re: [PATCH 5/6] arm64: dts: allwinner: a133: Add CPU OPP table
Date: Tue, 17 Nov 2026 23:52:52 +0100 [thread overview]
Message-ID: <f7752d1d155491876ae5d4bc1694c01c8d86b789.camel@sverdlin.org> (raw)
In-Reply-To: <20261104-a133-series-v1-5-58217cb33a87@gmail.com>
Hi Rajan!
On Wed, 2026-11-04 at 22:41 -0600, Rajan Yadav via B4 Relay wrote:
> From: Rajan Yadav <rajanyadav0307@gmail.com>
>
> Add the A133 CPU OPPs from the vendor BSP (sun50iw10p1.dtsi). There
> are ten voltage sets, speed0-5 for the a0-a5/a6 grades and speed6-9
> for the "high speed" b0-b3 grades. opp-supported-hw selects the
> frequencies of each grade:
>
> - 1464 MHz only for the a grades
> - 1416 and 1512 MHz only for the b grades
> - 408-1320 MHz for all
>
> The highest voltage is 1.18 V, inside the 0.81-1.2 V recommended
> operating range of VDD_CPU in the A133 datasheet (V1.5, table 5-2).
>
> The BSP uses 1008 MHz where the A100 table uses 1080 MHz, at the same
> voltages for a0-a2. U-Boot starts the CPU at 1008 MHz, which mainline
> now reports as an unlisted initial frequency. This table follows the
> BSP. The BSP table stops at 1512 MHz, so there is no 1608 MHz OPP,
> although some datasheet versions list 1.6 GHz for the A133. A newer
> factory kernel adds 1608 MHz for b0 and b1 only; that is left for a
> follow-up.
>
> The table has the A100 compatible as a fallback and the speed bin cell
> first, so a kernel without A133 support selects speed0-2 from the speed
> bin and gets the voltages of the A100 table, with 1008 instead of
> 1080 MHz. It needs the efuse cells added to sun50i-a100.dtsi in the
> previous patch.
>
> A script compared every voltage and the frequency set of every grade
> with the BSP file and found no difference.
>
> Claude Code (Anthropic) drafted this table and its message from the
> vendor BSP device tree (numbers only) and wrote the comparison script;
> I reviewed it and tested it on a KickPi K5C.
>
> Suggested-by: Andre Przywara <andre.przywara@arm.com>
> Signed-off-by: Rajan Yadav <rajanyadav0307@gmail.com>
Reviewed-by: Alexander Sverdlin <alex@sverdlin.org>
Tested-by: Alexander Sverdlin <alex@sverdlin.org>
> ---
> .../boot/dts/allwinner/sun50i-a133-cpu-opp.dtsi | 172 +++++++++++++++++++++
> 1 file changed, 172 insertions(+)
next prev parent reply other threads:[~2026-11-17 22:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 4:40 [PATCH 0/6] sunxi: A133: Add CPU speed grade detection and " Rajan Yadav via B4 Relay
2026-11-05 4:40 ` [PATCH 1/6] dt-bindings: opp: h6: Add A133 operating points Rajan Yadav via B4 Relay
2026-11-17 22:41 ` Alexander Sverdlin
2026-11-05 4:40 ` [PATCH 2/6] cpufreq: sun50i: Move nvmem cell reading into a helper Rajan Yadav via B4 Relay
2026-11-17 22:34 ` Alexander Sverdlin
2026-11-05 4:40 ` [PATCH 3/6] cpufreq: sun50i: Add A133 speed grade detection Rajan Yadav via B4 Relay
2026-11-17 22:38 ` Alexander Sverdlin
2026-11-05 4:40 ` [PATCH 4/6] arm64: dts: allwinner: a100: Add A133 speed grade efuse cells Rajan Yadav via B4 Relay
2026-11-17 22:38 ` Alexander Sverdlin
2026-11-05 4:41 ` [PATCH 5/6] arm64: dts: allwinner: a133: Add CPU OPP table Rajan Yadav via B4 Relay
2026-11-17 22:52 ` Alexander Sverdlin [this message]
2026-11-05 4:41 ` [PATCH 6/6] arm64: dts: allwinner: a133: Use the A133 " Rajan Yadav via B4 Relay
2026-11-17 22:41 ` Alexander Sverdlin
2026-11-05 11:30 ` [PATCH 0/6] sunxi: A133: Add CPU speed grade detection and " Andre Przywara
2026-11-05 14:49 ` Rajan Yadav
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=f7752d1d155491876ae5d4bc1694c01c8d86b789.camel@sverdlin.org \
--to=alex@sverdlin.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=masterr3c0rd@epochal.quest \
--cc=rajanyadav0307@gmail.com \
/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®