Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Paul Kocialkowski <paulk@sys-base.io>
Cc: linux-sunxi@lists.linux.dev,
	Andre Przywara <andre.przywara@arm.com>,
	 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: Mon, 18 May 2026 22:05:25 +0200	[thread overview]
Message-ID: <04da68168f92b196cce4d49c766fc62702bf6472.camel@gmail.com> (raw)
In-Reply-To: <agr9m_tidBr6Cu2h@collins>

Hi Paul,

thanks for the review!

On Mon, 2026-05-18 at 13:52 +0200, Paul Kocialkowski wrote:
> 
> > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a133-baije-core.dtsi b/arch/arm64/boot/dts/allwinner/sun50i-a133-baije-core.dtsi
> > new file mode 100644
> > index 000000000000..65b094f30bf5
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/allwinner/sun50i-a133-baije-core.dtsi

[]

> You should add:
> 
> 	chosen {
> 		stdout-path = "serial0:115200n8";
> 	};

I actually have it in .dts, but it's theoretically possible to deploy
the core board in a way that serial0 is *not* a console, so the above
probably will not be valid in all cases in .dtsi.

> 
> 
> 
> > +&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?

> 
> > +&reg_dcdc4 {
> > +	regulator-always-on;
> > +	regulator-min-microvolt = <500000>;
> > +	regulator-max-microvolt = <1300000>;
> > +	regulator-name = "vdd-sys";
> 
> Should be:
> 	regulator-min-microvolt = <810000>;
> 	regulator-max-microvolt = <990000>;
> 	regulator-name = "vcc-usb-sys";

I'm a bit puzzled here: datasheet says 0.9..1.0v
and it has no "Typ" value, similar to VDD_CPU, but
VDD_SYS is not part of OPP tables, so who is going
to adjust this? Or shall it be just

regulator-min-microvolt = <950000>;
regulator-max-microvolt = <950000>;

?

> 
> > +};
> > +
> > +&reg_dcdc5 {
> > +	regulator-always-on;
> > +	regulator-min-microvolt = <800000>;
> > +	regulator-max-microvolt = <1840000>;
> > +	regulator-name = "vcc-dram";
> 
> Should be:
> 	regulator-min-microvolt = <1100000>;
> 	regulator-max-microvolt = <1100000>;
> 	regulator-name = "vcc-dram-2";
> 
> ALDO2 is the main DRAM supply, this is the second one.

Core schematics mentions 1.1V/1.2/1.35/1.5 on this rail...
Currently U-Boot has CONFIG_AXP_DCDC5_VOLT=1100, but potentially
this is adjustable, right? At some point LPDDR4 chips they
are soldering today will be unavailable. And in the current
market it will happen rather sooner than later...

> 
> > +};
> > +
> > +/* DCDC6 unused */
> > +
> > +&reg_dldo1 {
> > +	regulator-min-microvolt = <700000>;
> > +	regulator-max-microvolt = <3300000>;
> > +	regulator-enable-ramp-delay = <1000>;
> 
> Should be:
> 	regulator-min-microvolt = <1800000>;
> 	regulator-max-microvolt = <1800000>;
> 	regulator-name = "vcc-pg";

Do suggest to drop vendor's

regulator-enable-ramp-delay = <1000>;

in all cases?

> > 
> > diff --git a/arch/arm64/boot/dts/allwinner/sun50i-a133-baijie-helper.dts b/arch/arm64/boot/dts/allwinner/sun50i-a133-baijie-helper.dts
> > new file mode 100644
> > index 000000000000..ccbca5d0a40c
> > --- /dev/null
> > +++ b/arch/arm64/boot/dts/allwinner/sun50i-a133-baijie-helper.dts

[]

> > +	aliases {
> > +		serial0 = &uart0;
> 
> The is best added to the core dtsi.
> 
> > +	};
> > +
> > +	chosen {
> > +		stdout-path = "serial0:115200n8";
> 
> Ditto.

But it only physically materializes in Helperboard, the carrier.
Potentially this one can be left floating or used for something else.

-- 
Alexander Sverdlin.


  parent reply	other threads:[~2026-05-18 20:05 UTC|newest]

Thread overview: 30+ 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 [this message]
2026-05-18 21:46       ` Paul Kocialkowski
2026-05-19  3:33         ` Chen-Yu Tsai
2026-05-18 21:54       ` Andre Przywara

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=04da68168f92b196cce4d49c766fc62702bf6472.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