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 1/6] dt-bindings: opp: h6: Add A133 operating points
Date: Tue, 17 Nov 2026 23:41:12 +0100	[thread overview]
Message-ID: <a11b490c84234b7c37d314e3cfa93434566e221e.camel@sverdlin.org> (raw)
In-Reply-To: <20261104-a133-series-v1-1-58217cb33a87@gmail.com>

Hi Rajan!

On Wed, 2026-11-04 at 22:40 -0600, Rajan Yadav via B4 Relay wrote:
> From: Rajan Yadav <rajanyadav0307@gmail.com>
> 
> The vendor BSP for the A100/A133 family (sun50iw10) selects the CPU
> speed grade from four efuse fields and the die revision: the speed bin
> (SID offset 0x1c, which also holds the ICPU current), the chip marking
> ID (0x00), a value programmed at production that the BSP calls PCPU
> (0x20) and a bin extension bit (0x28). It knows 11 grades, a0-a6 and
> b0-b3. The A100 operating points describe only three speed bins, taken
> from 0x1c.
> 
> Add allwinner,sun50i-a133-operating-points for this. In its tables the
> N of opp-microvolt-speedN is the vendor grade: 0-5 are a0-a5 (a6 has
> the same OPPs and voltages as a5) and 6-9 are b0-b3. The four cells are
> named, with the speed bin first. The meaning of the PCPU field is not
> documented; the name follows the vendor BSP.
> 
> Indices 0-2 are the vendor grades a0-a2, which have the voltages of the
> three A100 speed bins. So allwinner,sun50i-a100-operating-points is a
> valid fallback: software that knows only the A100 compatible reads the
> first cell, selects one of speed0-2 with the A100 rule and gets the
> OPPs and voltages of the A100 table today, with 1008 instead of
> 1080 MHz. That is the A100 selection, not the vendor's; the new
> compatible adds the vendor's. The binding requires indices 0-2 to stay
> usable this way.
> 
> The new compatible is SoC specific, like the root compatible
> allwinner,sun50i-a133; the A100 compatible stays as it is for existing
> DTBs. The schema now also limits the other compatibles to the single
> unnamed cell that all in-tree users have.
> 
> Claude Code (Anthropic) drafted this change and its message from the
> vendor BSP sources (field layout and numbers only, no code copied); I
> reviewed it and checked it with dt_binding_check and dtbs_check.
> 
> Signed-off-by: Rajan Yadav <rajanyadav0307@gmail.com>

Ran dtbs_check on it,

Tested-by: Alexander Sverdlin <alex@sverdlin.org>

> ---
>  .../opp/allwinner,sun50i-h6-operating-points.yaml  | 94 ++++++++++++++++++++--
>  1 file changed, 86 insertions(+), 8 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 OPP table 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 [this message]
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
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=a11b490c84234b7c37d314e3cfa93434566e221e.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®