Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Rakesh Kota" <rakesh.kota@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/3] arm64: dts: qcom: shikra: add vph_pwr and fix supply parent mappings
Date: Fri, 17 Jul 2026 05:45:28 +0000	[thread overview]
Message-ID: <20260717054529.9E0521F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260717-pm2250-fix-supply-parent-v1-3-a6213a42a3b5@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] Physically impossible hardware topology: 1.8V LDOs are configured to be supplied by a 1.396V source.
- [Medium] Missing parent supply properties for the s1 and s2 buck converters in the PM4125 regulator node.
--

--- Patch [3]: [PATCH 3/3] arm64: dts: qcom: shikra: add vph_pwr and fix supply parent mappings ---
commit 64d116ee25fe416f23ec9e23adfecfac498cc60e
Author: Rakesh Kota <rakesh.kota@oss.qualcomm.com>

arm64: dts: qcom: shikra: add vph_pwr and fix supply parent mappings

This commit adds a fixed vph_pwr regulator to represent the PM4125 charger
output. It also configures the per-group supply properties for the regulators
and adds the s1 and s4 nodes.

> diff --git a/arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi b/arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi
> index dc3861489f64d..6e4c23a730fb6 100644
> --- a/arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi
> +++ b/arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi
[ ... ]
> @@ -52,12 +62,33 @@ &pm8005_regulators {
>  &rpm_requests {
>  	regulators {
>  		compatible = "qcom,rpm-pm2250-regulators";
> +		vdd_s4-supply = <&vph_pwr>;
> +		vdd_l1-supply =  <&pm4125_s4>;

[Severity: Medium]
Are the parent supply properties for the s1 and s2 buck converters intentionally
omitted here?

Leaving out vdd_s1-supply and vdd_s2-supply prevents the regulator core from
resolving the full supply chain, which could lead to power management
dependencies failing if the parent supply is turned off while s1 or s2 are
active.

> +		vdd_l2_l3-supply =  <&pm4125_s4>;
> +		vdd_l5_l6_l7_l11_l12-supply =  <&pm4125_s4>;
> +		vdd_l8_l9-supply =  <&pm4125_s4>;
> +		vdd_l10-supply =  <&pm4125_s4>;
> +		vdd_l13_l14-supply =  <&pm4125_s1>;
> +		vdd_l15_l16-supply =  <&pm4125_s1>;

[Severity: High]
Is it possible to supply 1.8V LDOs from a 1.396V source?

The s1 regulator is configured with a 1.396V output later in this patch:

> +		pm4125_s1: s1 {
> +			regulator-min-microvolt = <1396000>;
> +			regulator-max-microvolt = <1396000>;
> +		};

But l13 through l16 are defined elsewhere in the file as requiring 1.8V:

arch/arm64/boot/dts/qcom/shikra-cqm-som.dtsi:regulators {
        pm4125_l13: l13 {
                regulator-min-microvolt = <1800000>;
                regulator-max-microvolt = <1800000>;
        };

Since a Low-Dropout Regulator (LDO) can only step down voltage, it seems like
supplying these LDOs from pm4125_s1 will prevent them from reaching their
target output voltage and cause hardware malfunction.

> +		vdd_l17_l22-supply = <&vph_pwr>;
> +		vdd_l18_l19-supply = <&vph_pwr>;
> +		vdd_l4_l20_l21-supply = <&vph_pwr>;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260717-pm2250-fix-supply-parent-v1-0-a6213a42a3b5@oss.qualcomm.com?part=3

      reply	other threads:[~2026-07-17  5:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-17  5:31 [PATCH 0/3] regulator: qcom_smd-regulator: fix PM2250 supply parent mappings Rakesh Kota
2026-07-17  5:31 ` [PATCH 1/3] " Rakesh Kota
2026-07-17  5:32 ` [PATCH 2/3] arm64: dts: qcom: qrb2210: fix PM4125 regulator " Rakesh Kota
2026-07-17  5:32 ` [PATCH 3/3] arm64: dts: qcom: shikra: add vph_pwr and fix " Rakesh Kota
2026-07-17  5:45   ` sashiko-bot [this message]

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=20260717054529.9E0521F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=rakesh.kota@oss.qualcomm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox