mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 6/6] arm64: dts: allwinner: a133: Use the A133 CPU OPP table
Date: Tue, 17 Nov 2026 23:41:03 +0100	[thread overview]
Message-ID: <9f30d506be74bf49626440a7f013a748dde3ec2d.camel@sverdlin.org> (raw)
In-Reply-To: <20261104-a133-series-v1-6-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>
> 
> Switch the three A133 boards in mainline (Baijie Helperboard A133,
> Liontron H-A133L and Teclast P80) from the A100 OPP table to the A133
> one, so the speed grade is selected as the vendor does it.
> 
> What changes depends on the chip:
> - revision A-E parts with a normal marking ID get a0-a2 from the bin
>   field, as they get speed0-2 today, with the same voltages; only
>   1080 MHz becomes 1008 MHz. The exception is a part whose ICPU and
>   PCPU values are in the range for which the BSP forces a0.
> - revision F and later parts with a normal marking ID get the a3-a6
>   voltages: higher at 408 and 600 MHz, equal or lower from 1008 MHz,
>   and 1008 instead of 1080 MHz.
> - "high speed" parts get the b grades, with 1416 and 1512 MHz instead
>   of 1464 MHz.
> - if the firmware does not provide SMCCC SOC_ID, the driver keeps the
>   A100 selection, adds the BSP's a0 rule for normal parts and warns at
>   boot.
> 
> All three boards supply the CPUs from AXP803 DCDC2 with a 0.81-1.2 V
> range, which covers every new voltage. Without the A133 support in
> sun50i-cpufreq-nvmem the A100 fallback applies. The Teclast P80 also
> needs "cpufreq: sun50i: Handle boards with the allwinner,sun50i-a133
> compatible" to get cpufreq at all.
> 
> Claude Code (Anthropic) drafted this change and its message; I
> reviewed it. I tested the A133 table on a KickPi K5C; I cannot test
> these three boards.
> 
> 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>

> ---
>  arch/arm64/boot/dts/allwinner/sun50i-a133-helperboard-core.dtsi | 2 +-
>  arch/arm64/boot/dts/allwinner/sun50i-a133-liontron-h-a133l.dts  | 2 +-
>  arch/arm64/boot/dts/allwinner/sun50i-a133-teclast-p80.dts       | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)

  reply	other threads:[~2026-11-17 22:41 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
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 [this message]
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=9f30d506be74bf49626440a7f013a748dde3ec2d.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®