Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Andre Heider" <a.heider@gmail.com>
Cc: krzk+dt@kernel.org, devicetree@vger.kernel.org,
	conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 1/6] riscv: dts: spacemit: k1-musepi-pro: add PMIC and power infrastructure
Date: Tue, 12 May 2026 02:14:42 +0000	[thread overview]
Message-ID: <20260512021443.347D1C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260511111116.1109643-2-a.heider@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The node name `regulator-vcc-40v` incorrectly implies a 40V regulator, whereas it is configured for 4.0V.
--

commit 31559fd8aa980bcda8336aa1515122f80207c34b
Author: Andre Heider <a.heider@gmail.com>

riscv: dts: spacemit: k1-musepi-pro: add PMIC and power infrastructure

This commit enables i2c8 and adds the connected SpacemiT P1 PMIC with
its related regulators for the board's power infrastructure.

> diff --git a/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts b/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
> --- a/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
> +++ b/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts

[ ... ]

> +	reg_vcc_4v0: regulator-vcc-40v {

This isn't a bug, but there appears to be a typo in the node name. The 40v
suffix implies a 40V regulator, whereas the regulator properties configure
it for 4.0V. Should this be named regulator-vcc-4v0 or similar to match the
label and configuration?

> +		compatible = "regulator-fixed";
> +		regulator-name = "VCC4V0";
> +		regulator-min-microvolt = <4000000>;
> +		regulator-max-microvolt = <4000000>;
> +		regulator-boot-on;
> +		regulator-always-on;
> +		vin-supply = <&reg_usb_vbus>;
> +	};

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260511111116.1109643-1-a.heider@gmail.com?part=1

  reply	other threads:[~2026-05-12  2:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260511111116.1109643-1-a.heider@gmail.com>
2026-05-11 11:11 ` [PATCH v2 1/6] riscv: dts: spacemit: k1-musepi-pro: add PMIC and power infrastructure Andre Heider
2026-05-12  2:14   ` sashiko-bot [this message]
2026-05-12 11:39   ` Yixun Lan
2026-05-12 12:20     ` Andre Heider
2026-05-11 11:11 ` [PATCH v2 2/6] riscv: dts: spacemit: k1-musepi-pro: add 24c04 eeprom Andre Heider
2026-05-12  2:18   ` sashiko-bot
2026-05-11 11:11 ` [PATCH v2 3/6] riscv: dts: spacemit: k1-musepi-pro: enable QSPI and add SPI NOR Andre Heider
2026-05-12  2:28   ` sashiko-bot
2026-05-12  6:51     ` Andre Heider
2026-05-12 11:55       ` Rob Herring
2026-05-12 12:18         ` Andre Heider
2026-05-12 11:44   ` Yixun Lan
2026-05-11 11:11 ` [PATCH v2 4/6] riscv: dts: spacemit: k1-musepi-pro: enable USB 3 ports Andre Heider
2026-05-11 11:11 ` [PATCH v2 5/6] riscv: dts: spacemit: k1-musepi-pro: enable PCIe ports Andre Heider
2026-05-12  4:02   ` sashiko-bot
2026-05-12 11:34   ` Yixun Lan
2026-05-11 11:11 ` [PATCH v2 6/6] riscv: dts: spacemit: k1-musepi-pro: set default console baud rate Andre Heider
2026-05-12 11:35   ` 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=20260512021443.347D1C2BCB0@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=a.heider@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox