From: Maud Spierings <maud_spierings@murena.io>
To: sandie.cao@deepcomputing.io
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, conor+dt@kernel.org,
devicetree@vger.kernel.org, dlan@kernel.org, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
palmer@dabbelt.com, pjw@kernel.org, robh@kernel.org,
spacemit@lists.linux.dev, troy.mitchell@linux.spacemit.com
Subject: Re: [PATCH v3 1/3] riscv: dts: spacemit: k3-deepcomputing-fml13v05: add P1 PMIC regulator tree
Date: Wed, 4 Nov 2026 16:31:06 +0100 [thread overview]
Message-ID: <5f595068-671e-4823-95af-da1702354a16@murena.io> (raw)
In-Reply-To: <20261102060105.100645-1-sandie.cao@deepcomputing.io>
Hi Sandie,
> Add the P1 PMIC's regulator topology tree for DeepComputing FML13V05 board
>
> Signed-off-by: Sandie Cao <sandie.cao@deepcomputing.io>
> ---
> .../spacemit/k3-deepcomputing-fml13v05.dts | 155 ++++++++++++++++++
> 1 file changed, 155 insertions(+)
>
> diff --git a/arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts b/arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts
> index b5d5112de358..804abc85602a 100644
> --- a/arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts
> +++ b/arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts
> @@ -22,6 +22,161 @@ memory@100000000 {
> device_type = "memory";
> reg = <0x1 0x00000000 0x4 0x00000000>;
> };
> +
> + reg_aux_vcc3v3: regulator-aux-vcc3v3 {
> + compatible = "regulator-fixed";
> + regulator-name = "AUX_VCC3V3";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + regulator-always-on;
> + };
> +
> + reg_aux_vcc5v: regulator-aux-vcc5v {
> + compatible = "regulator-fixed";
> + regulator-name = "AUX_VCC5V";
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + regulator-always-on;
> + };
> +};
> +
> +&i2c8 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&i2c8_cfg>;
> + status = "okay";
> +
> + p1@41 {
I believe this should be pmic@41
If it needs a label it could be p1: pmic@41 but the node name should be
more descriptive.
Kind regards,
Maud
WARNING: multiple messages have this Message-ID (diff)
From: Maud Spierings <maud_spierings@murena.io>
To: sandie.cao@deepcomputing.io
Cc: alex@ghiti.fr, aou@eecs.berkeley.edu, conor+dt@kernel.org,
devicetree@vger.kernel.org, dlan@kernel.org, krzk+dt@kernel.org,
linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
palmer@dabbelt.com, pjw@kernel.org, robh@kernel.org,
spacemit@lists.linux.dev, troy.mitchell@linux.spacemit.com
Subject: Re: [PATCH v3 1/3] riscv: dts: spacemit: k3-deepcomputing-fml13v05: add P1 PMIC regulator tree
Date: Wed, 4 Nov 2026 16:31:06 +0100 [thread overview]
Message-ID: <5f595068-671e-4823-95af-da1702354a16@murena.io> (raw)
In-Reply-To: <20261102060105.100645-1-sandie.cao@deepcomputing.io>
Hi Sandie,
> Add the P1 PMIC's regulator topology tree for DeepComputing FML13V05 board
>
> Signed-off-by: Sandie Cao <sandie.cao@deepcomputing.io>
> ---
> .../spacemit/k3-deepcomputing-fml13v05.dts | 155 ++++++++++++++++++
> 1 file changed, 155 insertions(+)
>
> diff --git a/arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts b/arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts
> index b5d5112de358..804abc85602a 100644
> --- a/arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts
> +++ b/arch/riscv/boot/dts/spacemit/k3-deepcomputing-fml13v05.dts
> @@ -22,6 +22,161 @@ memory@100000000 {
> device_type = "memory";
> reg = <0x1 0x00000000 0x4 0x00000000>;
> };
> +
> + reg_aux_vcc3v3: regulator-aux-vcc3v3 {
> + compatible = "regulator-fixed";
> + regulator-name = "AUX_VCC3V3";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + regulator-always-on;
> + };
> +
> + reg_aux_vcc5v: regulator-aux-vcc5v {
> + compatible = "regulator-fixed";
> + regulator-name = "AUX_VCC5V";
> + regulator-min-microvolt = <5000000>;
> + regulator-max-microvolt = <5000000>;
> + regulator-always-on;
> + };
> +};
> +
> +&i2c8 {
> + pinctrl-names = "default";
> + pinctrl-0 = <&i2c8_cfg>;
> + status = "okay";
> +
> + p1@41 {
I believe this should be pmic@41
If it needs a label it could be p1: pmic@41 but the node name should be
more descriptive.
Kind regards,
Maud
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2026-11-04 15:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 6:00 [PATCH v3 0/3] Enable USB and SD for Deepcomputing FML13V05 board Sandie Cao
2026-11-02 6:00 ` Sandie Cao
2026-11-02 6:01 ` [PATCH v3 1/3] riscv: dts: spacemit: k3-deepcomputing-fml13v05: add P1 PMIC regulator tree Sandie Cao
2026-11-02 6:01 ` Sandie Cao
2026-11-02 17:00 ` sashiko-bot
2026-11-04 15:31 ` Maud Spierings [this message]
2026-11-04 15:31 ` Maud Spierings
2026-11-05 1:46 ` Sandie Cao
2026-11-05 1:46 ` Sandie Cao
2026-11-02 6:01 ` [PATCH v3 2/3] riscv: dts: spacemit: k3-deepcomputing-fml13v05: add USB controller and USB phy support Sandie Cao
2026-11-02 6:01 ` Sandie Cao
2026-11-02 6:01 ` [PATCH v3 3/3] riscv: dts: spacemit: k3-deepcomputing-fml13v05: Enable SD card support Sandie Cao
2026-11-02 6:01 ` Sandie Cao
2026-11-05 1:19 ` Troy Mitchell
2026-11-05 1:19 ` Troy Mitchell
2026-11-05 1:33 ` Sandie Cao
2026-11-05 1:33 ` Sandie Cao
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=5f595068-671e-4823-95af-da1702354a16@murena.io \
--to=maud_spierings@murena.io \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlan@kernel.org \
--cc=krzk+dt@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=sandie.cao@deepcomputing.io \
--cc=spacemit@lists.linux.dev \
--cc=troy.mitchell@linux.spacemit.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 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.