Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Gopikishan Thawre" <gopikishan.thawre@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 2/3] arm64: dts: qcom: lemans: Add Draco EVK SoM platform
Date: Tue, 20 Oct 2026 10:28:24 +0000	[thread overview]
Message-ID: <sashiko-outbox-178837@kernel.org> (raw)
In-Reply-To: <20261019-lemans-draco-final-changes-bringup-v1-2-dcabe94f1074@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] arm64: dts: qcom: lemans-draco-evk-som: swapped USB QMP PHY supplies
--

commit 8560cf8c07ec29ddb7e6a2feb1b5ebde75e47b48
Author: Gopikishan Thawre <gopikishan.thawre@oss.qualcomm.com>

arm64: dts: qcom: lemans: Add Draco EVK SoM platform

This commit introduces the device tree for the SA8775P/QCS9100-based LeMans
Draco EVK SoM, configuring RPMH regulators, remoteproc instances, UFS, USB,
GPU, and video processing unit nodes.

> diff --git a/arch/arm64/boot/dts/qcom/lemans-draco-evk-som.dtsi b/arch/arm64/boot/dts/qcom/lemans-draco-evk-som.dtsi
> new file mode 100644
> index 0000000000000..6b7971bcdc934
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/lemans-draco-evk-som.dtsi
> @@ -0,0 +1,401 @@

[ ... ]

> +&ufs_mem_phy {
> +	vdda-phy-supply = <&vreg_l4a>;
> +	vdda-pll-supply = <&vreg_l1c>;
> +
> +	status = "okay";
> +};
> +
> +&usb_0 {
> +	status = "okay";
> +};
> +
> +&usb_0_hsphy {
> +	vdda-pll-supply = <&vreg_l7a>;
> +	vdda18-supply = <&vreg_l6c>;
> +	vdda33-supply = <&vreg_l9a>;
> +
> +	status = "okay";
> +};
> +
> +&usb_0_qmpphy {
> +	vdda-phy-supply = <&vreg_l1c>;
> +	vdda-pll-supply = <&vreg_l7a>;
> +
> +	status = "okay";
> +};
> +
> +&usb_1 {
> +	dr_mode = "host";
> +
> +	status = "okay";
> +};
> +
> +&usb_1_hsphy {
> +	vdda-pll-supply = <&vreg_l7a>;
> +	vdda18-supply = <&vreg_l6c>;
> +	vdda33-supply = <&vreg_l9a>;
> +
> +	status = "okay";
> +};
> +
> +&usb_1_qmpphy {
> +	vdda-phy-supply = <&vreg_l1c>;
> +	vdda-pll-supply = <&vreg_l7a>;
> +
> +	status = "okay";
> +};

[Severity: Medium]
Are vdda-phy-supply and vdda-pll-supply swapped in both usb_0_qmpphy and
usb_1_qmpphy?

Earlier in this file, vreg_l7a is configured as the 0.72V-0.95V rail and
vreg_l1c is configured as the 1.14V-1.26V rail:

    vreg_l7a: ldo7 {
        regulator-name = "vreg_l7a";
        regulator-min-microvolt = <720000>;
        regulator-max-microvolt = <950000>;
        ...
    };

    vreg_l1c: ldo1 {
        regulator-name = "vreg_l1c";
        regulator-min-microvolt = <1140000>;
        regulator-max-microvolt = <1260000>;
        ...
    };

On SA8775P/QCS9100 QMP PHYs, vdda-phy-supply is the lower-voltage (~0.88V)
core supply and vdda-pll-supply is the higher-voltage (~1.2V) PLL supply
(matching ufs_mem_phy above, as well as the fix for other LeMans boards in
commit 932113c3c778 ("arm64: dts: qcom: lemans: Fix swapped USB QMP PHY
vdda-phy/vdda-pll supplies")).

In drivers/phy/qualcomm/phy-qcom-qmp-usb.c, qmp_phy_vreg_l[] specifies
different initial loads for the two supplies:

    static const struct regulator_bulk_data qmp_phy_vreg_l[] = {
        { .supply = "vdda-phy", .init_load_uA = 21800, },
        { .supply = "vdda-pll", .init_load_uA = 36000, },
    };

Because both vreg_l7a and vreg_l1c set regulator-allow-set-load, having these
supplies swapped causes the PHY driver to vote the 21.8 mA PHY load onto the
1.2V PLL rail (vreg_l1c) and the 36 mA PLL load onto the 0.88V PHY core rail
(vreg_l7a).

Should both usb_0_qmpphy and usb_1_qmpphy use vdda-phy-supply = <&vreg_l7a>
and vdda-pll-supply = <&vreg_l1c> instead?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261019-lemans-draco-final-changes-bringup-v1-0-dcabe94f1074@oss.qualcomm.com?part=2

  reply	other threads:[~2026-10-20 10:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 10:27 [PATCH 0/3] Add support for LeMans Draco EVK board Gopikishan Thawre
2026-10-19 10:27 ` [PATCH 1/3] dt-bindings: arm: qcom: Add " Gopikishan Thawre
2026-10-20  7:51   ` Krzysztof Kozlowski
2026-10-19 10:27 ` [PATCH 2/3] arm64: dts: qcom: lemans: Add Draco EVK SoM platform Gopikishan Thawre
2026-10-20 10:28   ` sashiko-bot [this message]
2026-10-19 10:27 ` [PATCH 3/3] arm64: dts: qcom: lemans: Add Draco EVK board Gopikishan Thawre
2026-10-19 12:05   ` Dmitry Baryshkov
2026-10-19 12:31   ` Konrad Dybcio
2026-10-20 10:28   ` sashiko-bot

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=sashiko-outbox-178837@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gopikishan.thawre@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