Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Andre Przywara <andre.przywara@arm.com>
Cc: Paul Kocialkowski <paulk@sys-base.io>,
	linux-sunxi@lists.linux.dev,  devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	 linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] arm64: dts: allwinner: A133: add support for Baijie Helper A133 board
Date: Fri, 05 Jun 2026 00:37:40 +0200	[thread overview]
Message-ID: <36c392676bc5cd69de5e8ca2cabe5ccbbced7517.camel@gmail.com> (raw)
In-Reply-To: <20260518235432.07537260@ryzen.lan>

Hi Andre,

On Mon, 2026-05-18 at 23:54 +0200, Andre Przywara wrote:
> > > > +&reg_dcdc2 {
> > > > +	regulator-always-on;
> > > > +	regulator-min-microvolt = <500000>;
> > > > +	regulator-max-microvolt = <1300000>;  
> > > 
> > > Should be:
> > >  	regulator-min-microvolt = <900000>;
> > >  	regulator-max-microvolt = <1300000>;  
> > 
> > 0.81..1.2v according to A133 Datasheet Revision 1.1 Jul.14, 2020?
> 
> Do you have the CPU OPPs for this board? Do they slightly
> overclock/over-volt the core? We have seen this for some other boards.
> But you could go with the safer 810mV...1200mV range, and we adjust
> this when needed.

I'm not sure how to interpret this, if it helps, vendor BSP has:

root@HelperA133:~# hexdump -Cv /proc/device-tree/opp_l_table/opp@1512000000/
clock-latency-ns  name              opp-hz            opp-microvolt-b0  opp-microvolt-b1  opp-microvolt-b2  opp-microvolt-b3  
root@HelperA133:~# hexdump -Cv /proc/device-tree/opp_l_table/opp@1512000000/opp-microvolt-b0
00000000  00 12 01 60                                       |...`|
root@HelperA133:~# hexdump -Cv /proc/device-tree/opp_l_table/opp@1512000000/opp-microvolt-b1
00000000  00 11 3e 10 00 11 3e 10  00 11 65 20              |..>...>...e |
root@HelperA133:~# hexdump -Cv /proc/device-tree/opp_l_table/opp@1512000000/opp-microvolt-b2
00000000  00 10 c8 e0                                       |....|
root@HelperA133:~# hexdump -Cv /proc/device-tree/opp_l_table/opp@1512000000/opp-microvolt-b3
00000000  00 10 7a c0                                       |..z.|
root@HelperA133:~# hexdump -Cv /proc/device-tree/opp_l_table/compatible 
00000000  61 6c 6c 77 69 6e 6e 65  72 2c 73 75 6e 35 30 69  |allwinner,sun50i|
00000010  2d 6f 70 65 72 61 74 69  6e 67 2d 70 6f 69 6e 74  |-operating-point|
00000020  73 00                                             |s.|

At least 1512MHz is possible (but datasheet says 1.6GHz, so probably no overclocking yet).

-- 
Alexander Sverdlin.


      reply	other threads:[~2026-06-04 22:38 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 20:16 [PATCH v2 0/3] Add support for Baijie Helper A133 board Alexander Sverdlin
2026-05-10 20:16 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Shenzhen Baijie Technology Co., Ltd Alexander Sverdlin
2026-05-18 11:36   ` Paul Kocialkowski
2026-05-10 20:16 ` [PATCH v2 2/3] dt-bindings: arm: sunxi: Add Baijie HelperBoard A133 compatible Alexander Sverdlin
2026-05-11 16:08   ` Conor Dooley
2026-05-11 16:18     ` Alexander Sverdlin
2026-05-11 16:34       ` Conor Dooley
2026-05-18 11:35   ` Paul Kocialkowski
2026-05-10 20:16 ` [PATCH v2 3/3] arm64: dts: allwinner: A133: add support for Baijie Helper A133 board Alexander Sverdlin
2026-05-11 11:44   ` Andre Przywara
2026-05-17 20:38     ` Alexander Sverdlin
2026-05-18  3:30       ` Chen-Yu Tsai
2026-05-18 10:12         ` Alexander Sverdlin
2026-05-18 11:16       ` Andre Przywara
2026-05-18 11:29         ` Alexander Sverdlin
2026-05-18 11:54           ` Paul Kocialkowski
2026-05-18 12:50           ` Andre Przywara
2026-05-18 14:47         ` Chen-Yu Tsai
2026-05-18 14:51           ` Alexander Sverdlin
2026-05-18 11:52   ` Paul Kocialkowski
2026-05-18 12:09     ` Alexander Sverdlin
2026-05-18 14:14       ` Paul Kocialkowski
2026-05-18 14:40         ` Alexander Sverdlin
2026-05-18 14:56           ` Paul Kocialkowski
2026-05-18 15:04             ` Alexander Sverdlin
2026-05-18 21:23           ` Andre Przywara
2026-05-18 20:05     ` Alexander Sverdlin
2026-05-18 21:46       ` Paul Kocialkowski
2026-05-19  3:33         ` Chen-Yu Tsai
2026-05-18 21:54       ` Andre Przywara
2026-06-04 22:37         ` Alexander Sverdlin [this message]

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=36c392676bc5cd69de5e8ca2cabe5ccbbced7517.camel@gmail.com \
    --to=alexander.sverdlin@gmail.com \
    --cc=andre.przywara@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=paulk@sys-base.io \
    /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