All of lore.kernel.org
 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, robh@kernel.org,
	conor+dt@kernel.org
Subject: Re: [PATCH v3 1/6] riscv: dts: spacemit: k1-musepi-pro: add PMIC and power infrastructure
Date: Thu, 14 May 2026 02:28:16 +0000	[thread overview]
Message-ID: <20260514022817.2FCF8C2BCB3@smtp.kernel.org> (raw)
In-Reply-To: <20260513071958.29574-2-a.heider@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Regulator minimum voltage constraints are set too loosely on fixed board rails, risking hardware brownouts.
--

commit 823adf1d7b0f1286cdd0e228119b713b02c36d2e
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 and voltage
regulation support.

> diff --git a/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts b/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
> index 29e333b670cf0..e0b585c50014b 100644
> --- a/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
> +++ b/arch/riscv/boot/dts/spacemit/k1-musepi-pro.dts
[ ... ]
> @@ -72,6 +82,130 @@ &pdma {
>  	status = "okay";
>  };
>  
> +&i2c8 {
> +	pinctrl-0 = <&i2c8_cfg>;
> +	pinctrl-names = "default";
> +	status = "okay";
> +
> +	pmic@41 {
> +		compatible = "spacemit,p1";
> +		reg = <0x41>;
> +		interrupts = <64>;
[ ... ]
> +		dldoin1-supply = <&buck5>;
> +		dldoin2-supply = <&buck5>;
> +
> +		regulators {
[ ... ]
> +			buck3_1v8: buck3 {
> +				regulator-min-microvolt = <500000>;
> +				regulator-max-microvolt = <1800000>;

Should these minimum bounds be restricted to match the exact hardware layout
of the board?

The labels buck3_1v8 and buck4_3v3 indicate these rails are wired for fixed
1.8V and 3.3V usage, but the regulator-min-microvolt allows them to scale
down to 0.5V. Could this loose constraint risk hardware brownouts if a driver
attempts dynamic voltage scaling on these rails?

> +				regulator-ramp-delay = <5000>;
> +				regulator-always-on;
> +			};
> +
> +			buck4_3v3: buck4 {
> +				regulator-min-microvolt = <500000>;
> +				regulator-max-microvolt = <3300000>;
> +				regulator-ramp-delay = <5000>;
> +				regulator-always-on;
> +			};
> +
> +			buck5: buck5 {
> +				regulator-min-microvolt = <500000>;
> +				regulator-max-microvolt = <3450000>;

Since buck5 is used as the parent supply for the DLDOs (dldoin1-supply and
dldoin2-supply), could the wide 0.5V minimum constraint allow the OS to drop
its voltage below the necessary headroom needed to power the downstream
DLDOs?

> +				regulator-ramp-delay = <5000>;
> +				regulator-always-on;
> +			};

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

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

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-13  7:19 [PATCH v3 0/6] spacemit: k1-musepi-pro: add missing devices Andre Heider
2026-05-13  7:19 ` Andre Heider
2026-05-13  7:19 ` [PATCH v3 1/6] riscv: dts: spacemit: k1-musepi-pro: add PMIC and power infrastructure Andre Heider
2026-05-13  7:19   ` Andre Heider
2026-05-13  7:48   ` Yixun Lan
2026-05-13  7:48     ` Yixun Lan
2026-05-13  8:02   ` Yixun Lan
2026-05-13  8:02     ` Yixun Lan
2026-05-14  2:28   ` sashiko-bot [this message]
2026-05-13  7:19 ` [PATCH v3 2/6] riscv: dts: spacemit: k1-musepi-pro: add 24c02 eeprom Andre Heider
2026-05-13  7:19   ` Andre Heider
2026-05-13  7:19 ` [PATCH v3 3/6] riscv: dts: spacemit: k1-musepi-pro: enable QSPI and add SPI NOR Andre Heider
2026-05-13  7:19   ` Andre Heider
2026-05-14  2:53   ` sashiko-bot
2026-05-13  7:19 ` [PATCH v3 4/6] riscv: dts: spacemit: k1-musepi-pro: enable USB 3 ports Andre Heider
2026-05-13  7:19   ` Andre Heider
2026-05-13  7:19 ` [PATCH v3 5/6] riscv: dts: spacemit: k1-musepi-pro: enable PCIe ports Andre Heider
2026-05-13  7:19   ` Andre Heider
2026-05-13  7:19 ` [PATCH v3 6/6] riscv: dts: spacemit: k1-musepi-pro: set default console baud rate Andre Heider
2026-05-13  7:19   ` Andre Heider
2026-05-13  7:46 ` [PATCH v3 0/6] spacemit: k1-musepi-pro: add missing devices Yixun Lan
2026-05-13  7:46   ` Yixun Lan
2026-05-13  7:56   ` Andre Heider
2026-05-13  7:56     ` Andre Heider

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=20260514022817.2FCF8C2BCB3@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-reviews@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.