From: Yixun Lan <dlan@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dts: riscv: spacemit: k3: add P1 PMIC regulator tree
Date: Thu, 26 Mar 2026 07:48:35 +0800 [thread overview]
Message-ID: <20260325234835-GKA777612@kernel.org> (raw)
In-Reply-To: <6530526f-59ca-4753-a068-46c62a1a1fed@kernel.org>
Hi Krzysztof,
On 14:54 Wed 25 Mar , Krzysztof Kozlowski wrote:
> On 25/03/2026 10:56, Yixun Lan wrote:
> > Add the P1 PMIC's regulator topology tree for pico-itx board.
> >
> > Signed-off-by: Yixun Lan <dlan@kernel.org>
> > ---
> > This series try to add a regulator power tree from P1 PMIC,
> > the PMIC is controlled via an I2C interface.
> >
> > To test this patch, it will need the I2C patch series [1]
> >
> > Link: https://lore.kernel.org/all/20260325-02-k3-i2c-v1-0-78f29c83d9ac@kernel.org [1]
> > ---
> > arch/riscv/boot/dts/spacemit/k3-pico-itx.dts | 185 +++++++++++++++++++++++++++
> > arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi | 11 ++
> > 2 files changed, 196 insertions(+)
> >
> > diff --git a/arch/riscv/boot/dts/spacemit/k3-pico-itx.dts b/arch/riscv/boot/dts/spacemit/k3-pico-itx.dts
> > index b098dbd0e7a1..5b59c569dbde 100644
> > --- a/arch/riscv/boot/dts/spacemit/k3-pico-itx.dts
> > +++ b/arch/riscv/boot/dts/spacemit/k3-pico-itx.dts
> > @@ -23,6 +23,191 @@ memory@100000000 {
> > device_type = "memory";
> > reg = <0x1 0x00000000 0x4 0x00000000>;
> > };
> > +
> > + reg_dc_in: regulator-dc-in-12v {
> > + compatible = "regulator-fixed";
> > + regulator-name = "dc_in_12v";
> > + regulator-min-microvolt = <12000000>;
> > + regulator-max-microvolt = <12000000>;
> > + regulator-boot-on;
> > + regulator-always-on;
> > + };
>
> This is a pointless supply. It's non-controllable and serves no devices,
Yes.. I thought to describe a more complete regulator tree, it just
shows more information - e.g. from $debugfs/regulator_summary
> so it only bloats the DTB and slows down boot process without any benefits.
Ok, I will drop it then
>
>
>
> > +
> > + reg_aux_vcc3v3: regulator-aux-vcc3v3 {
>
> This is even more pointless because there is no user. Dead code.
>
reg_aux_vcc3v3 is used by various devices, but I can drop it too,
leaves till there is device really needed..
> > + compatible = "regulator-fixed";
> > + regulator-name = "AUX_VCC3V3";
> > + regulator-min-microvolt = <3300000>;
> > + regulator-max-microvolt = <3300000>;
> > + regulator-always-on;
> > + vin-supply = <®_dc_in>;
> > + };
> >
>
>
> Best regards,
> Krzysztof
--
Yixun Lan (dlan)
WARNING: multiple messages have this Message-ID (diff)
From: Yixun Lan <dlan@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
spacemit@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dts: riscv: spacemit: k3: add P1 PMIC regulator tree
Date: Thu, 26 Mar 2026 07:48:35 +0800 [thread overview]
Message-ID: <20260325234835-GKA777612@kernel.org> (raw)
In-Reply-To: <6530526f-59ca-4753-a068-46c62a1a1fed@kernel.org>
Hi Krzysztof,
On 14:54 Wed 25 Mar , Krzysztof Kozlowski wrote:
> On 25/03/2026 10:56, Yixun Lan wrote:
> > Add the P1 PMIC's regulator topology tree for pico-itx board.
> >
> > Signed-off-by: Yixun Lan <dlan@kernel.org>
> > ---
> > This series try to add a regulator power tree from P1 PMIC,
> > the PMIC is controlled via an I2C interface.
> >
> > To test this patch, it will need the I2C patch series [1]
> >
> > Link: https://lore.kernel.org/all/20260325-02-k3-i2c-v1-0-78f29c83d9ac@kernel.org [1]
> > ---
> > arch/riscv/boot/dts/spacemit/k3-pico-itx.dts | 185 +++++++++++++++++++++++++++
> > arch/riscv/boot/dts/spacemit/k3-pinctrl.dtsi | 11 ++
> > 2 files changed, 196 insertions(+)
> >
> > diff --git a/arch/riscv/boot/dts/spacemit/k3-pico-itx.dts b/arch/riscv/boot/dts/spacemit/k3-pico-itx.dts
> > index b098dbd0e7a1..5b59c569dbde 100644
> > --- a/arch/riscv/boot/dts/spacemit/k3-pico-itx.dts
> > +++ b/arch/riscv/boot/dts/spacemit/k3-pico-itx.dts
> > @@ -23,6 +23,191 @@ memory@100000000 {
> > device_type = "memory";
> > reg = <0x1 0x00000000 0x4 0x00000000>;
> > };
> > +
> > + reg_dc_in: regulator-dc-in-12v {
> > + compatible = "regulator-fixed";
> > + regulator-name = "dc_in_12v";
> > + regulator-min-microvolt = <12000000>;
> > + regulator-max-microvolt = <12000000>;
> > + regulator-boot-on;
> > + regulator-always-on;
> > + };
>
> This is a pointless supply. It's non-controllable and serves no devices,
Yes.. I thought to describe a more complete regulator tree, it just
shows more information - e.g. from $debugfs/regulator_summary
> so it only bloats the DTB and slows down boot process without any benefits.
Ok, I will drop it then
>
>
>
> > +
> > + reg_aux_vcc3v3: regulator-aux-vcc3v3 {
>
> This is even more pointless because there is no user. Dead code.
>
reg_aux_vcc3v3 is used by various devices, but I can drop it too,
leaves till there is device really needed..
> > + compatible = "regulator-fixed";
> > + regulator-name = "AUX_VCC3V3";
> > + regulator-min-microvolt = <3300000>;
> > + regulator-max-microvolt = <3300000>;
> > + regulator-always-on;
> > + vin-supply = <®_dc_in>;
> > + };
> >
>
>
> Best regards,
> Krzysztof
--
Yixun Lan (dlan)
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-03-25 23:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 9:56 [PATCH] dts: riscv: spacemit: k3: add P1 PMIC regulator tree Yixun Lan
2026-03-25 9:56 ` Yixun Lan
2026-03-25 13:54 ` Krzysztof Kozlowski
2026-03-25 13:54 ` Krzysztof Kozlowski
2026-03-25 23:48 ` Yixun Lan [this message]
2026-03-25 23:48 ` Yixun Lan
2026-03-26 7:02 ` Krzysztof Kozlowski
2026-03-26 7:02 ` Krzysztof Kozlowski
2026-03-26 7:14 ` Yixun Lan
2026-03-26 7:14 ` Yixun Lan
2026-03-26 7:15 ` Krzysztof Kozlowski
2026-03-26 7:15 ` Krzysztof Kozlowski
2026-03-26 7:27 ` Yixun Lan
2026-03-26 7:27 ` Yixun Lan
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=20260325234835-GKA777612@kernel.org \
--to=dlan@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robh@kernel.org \
--cc=spacemit@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.