Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mohd Ayaan Anwar" <mohd.anwar@oss.qualcomm.com>
Cc: conor+dt@kernel.org, neil.armstrong@linaro.org, vkoul@kernel.org,
	linux-phy@lists.infradead.org, robh@kernel.org,
	olteanv@gmail.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 5/6] arm64: dts: qcom: monaco-evk: fix SerDes PHY regulator supplies
Date: Mon, 03 Aug 2026 19:47:37 +0000	[thread overview]
Message-ID: <20260803194738.4E0D51F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260804-b4-sgmiieth_serdes_regulator-v2-5-c4bc688177dd@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Incomplete device tree migration causes a functional regression on qcs8300-ride and monaco-monza-som boards, where the SerDes PHY will fail to power up because its 0.9V regulator rail is not enabled.
--

--- Patch [5]: [PATCH v2 5/6] arm64: dts: qcom: monaco-evk: fix SerDes PHY regulator supplies ---
commit 77126601ae0cd79ff3e3276e8f35420b21a2d2f5
Author: Mohd Ayaan Anwar <mohd.anwar@oss.qualcomm.com>

arm64: dts: qcom: monaco-evk: fix SerDes PHY regulator supplies

The commit updates the SerDes PHY node in the monaco-evk device tree to use
explicit named regulator supplies (vdda-0p9-supply and vdda-1p2-supply)
instead of the deprecated phy-supply property. This ensures both required
rails are properly described and enabled.

> diff --git a/arch/arm64/boot/dts/qcom/monaco-evk.dts b/arch/arm64/boot/dts/qcom/monaco-evk.dts
> index 9d17ef7d2caf1..f787e78b35ce4 100644
> --- a/arch/arm64/boot/dts/qcom/monaco-evk.dts
> +++ b/arch/arm64/boot/dts/qcom/monaco-evk.dts
> @@ -706,7 +706,8 @@ &sdhc_1 {
>  };
>  
>  &serdes0 {
> -	phy-supply = <&vreg_l4a>;
> +	vdda-0p9-supply = <&vreg_l4a>;
> +	vdda-1p2-supply = <&vreg_l5a>;

[Severity: High]
Does this migration to vdda-0p9-supply and vdda-1p2-supply need to be applied
to other boards as well?

Looking at arch/arm64/boot/dts/qcom/qcs8300-ride.dts and
arch/arm64/boot/dts/qcom/monaco-monza-som.dtsi, they still use the deprecated
phy-supply property for serdes0:

arch/arm64/boot/dts/qcom/qcs8300-ride.dts:serdes0 {
	phy-supply = <&vreg_l5a>;
	status = "okay";
};

If the qcom-dwmac-sgmii-phy driver was updated in this series to require
explicit vdda-0p9 and vdda-1p2 supplies, devm_regulator_bulk_get_const() will
fall back to dummy regulators for these missing named supplies.

This would leave the 0.9V physical rail unpowered on these other boards, which
causes the PHY calibration to time out and the Ethernet interface to fail to
initialize.

Should these device trees also be updated to ensure their SerDes PHYs do not
fail to power up?

>  
>  	status = "okay";
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260804-b4-sgmiieth_serdes_regulator-v2-0-c4bc688177dd@oss.qualcomm.com?part=5

  reply	other threads:[~2026-08-03 19:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03 19:27 [PATCH v2 0/6] Fix regulator voting for the Qualcomm SGMII SerDes PHY Mohd Ayaan Anwar
2026-08-03 19:27 ` [PATCH v2 1/6] dt-bindings: phy: qcom,sa8775p-dwmac-sgmii-phy: add named voltage rails and deprecate phy-supply Mohd Ayaan Anwar
2026-08-03 19:36   ` sashiko-bot
2026-08-04  6:19   ` Krzysztof Kozlowski
2026-08-03 19:27 ` [PATCH v2 2/6] phy: qcom: sgmii-eth: vote for both voltage rails with correct current loads Mohd Ayaan Anwar
2026-08-03 19:38   ` sashiko-bot
2026-08-03 19:27 ` [PATCH v2 3/6] arm64: dts: qcom: lemans-evk: fix SerDes PHY regulator supplies Mohd Ayaan Anwar
2026-08-03 19:37   ` sashiko-bot
2026-08-03 19:28 ` [PATCH v2 4/6] arm64: dts: qcom: lemans-ride-common: " Mohd Ayaan Anwar
2026-08-03 19:43   ` sashiko-bot
2026-08-03 19:28 ` [PATCH v2 5/6] arm64: dts: qcom: monaco-evk: " Mohd Ayaan Anwar
2026-08-03 19:47   ` sashiko-bot [this message]
2026-08-03 19:28 ` [PATCH v2 6/6] arm64: dts: qcom: qcs8300-ride: " Mohd Ayaan Anwar
2026-08-03 19:36   ` sashiko-bot
2026-08-04  8:36 ` [PATCH v2 0/6] Fix regulator voting for the Qualcomm SGMII SerDes PHY Mohd Ayaan Anwar

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=20260803194738.4E0D51F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=mohd.anwar@oss.qualcomm.com \
    --cc=neil.armstrong@linaro.org \
    --cc=olteanv@gmail.com \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=vkoul@kernel.org \
    /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