Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Manivannan Sadhasivam" <manivannan.sadhasivam@oss.qualcomm.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 28/28] arm64: dts: qcom: talos-evk: Fix swapped USB QMP PHY vdda-phy/vdda-pll supplies
Date: Mon, 03 Aug 2026 07:01:59 +0000	[thread overview]
Message-ID: <20260803070159.771841F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260803-phy-supply-fix-v1-28-5880630cde3e@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:

Pre-existing issues:
- [High] This problem wasn't introduced by this patch, but the patch provides an incomplete fix that leaves several QMP PHYs incorrectly configured. The commit message states that the QMP PHY expects the `vdda-pll` supply to be 1.2V, and the patch correctly sets `usb_qmpphy_2` to use `vreg_l11a` (which is configured for 1.23V - 1.26V). However, it fails to fix `usb_qmpphy`, `ufs_mem_phy`, and `pcie_phy` in the same file (`talos-evk-som.dtsi`), all of which continue to use `vreg_l12a` (which is configured for 1.8V - 1.89V) for their PLL supply. Furthermore, the sibling board `qcs615-ride.dts` also leaves both `usb_qmpphy` and `usb_qmpphy_2` configured with `vreg_l12a` (1.8V). This leaves the remaining PHYs exposed to a significant overvoltage (1.8V instead of 1.2V).
--

--- Patch [28]: [PATCH 28/28] arm64: dts: qcom: talos-evk: Fix swapped USB QMP PHY vdda-phy/vdda-pll supplies ---
commit a8da26c25bde26c79bbdbc3a2692464d3f213cfd
Author: Manivannan Sadhasivam <manivannan.sadhasivam@oss.qualcomm.com>

arm64: dts: qcom: talos-evk: Fix swapped USB QMP PHY vdda-phy/vdda-pll supplies

This commit corrects the swapped vdda-phy and vdda-pll supplies for the USB
QMP PHY on the QCS615 Talos EVK board. The patch ensures the vdda-pll supply
is fed 1.2V instead of 0.9V.

> diff --git a/arch/arm64/boot/dts/qcom/talos-evk-som.dtsi b/arch/arm64/boot/dts/qcom/talos-evk-som.dtsi
> index 294354c034c37..6469c6fa9f634 100644
> --- a/arch/arm64/boot/dts/qcom/talos-evk-som.dtsi
> +++ b/arch/arm64/boot/dts/qcom/talos-evk-som.dtsi
> @@ -589,8 +589,8 @@ &usb_qmpphy {
>  };
>  
>  &usb_qmpphy_2 {
> -	vdda-phy-supply = <&vreg_l11a>;
> -	vdda-pll-supply = <&vreg_l5a>;
> +	vdda-phy-supply = <&vreg_l5a>;
> +	vdda-pll-supply = <&vreg_l11a>;

[Severity: High]
This isn't a bug introduced by this patch, but does this provide an
incomplete fix that leaves several other QMP PHYs incorrectly configured?

The commit message states that the QMP PHY expects the vdda-pll supply to
be 1.2V, and this patch updates usb_qmpphy_2 to use vreg_l11a (1.23V - 1.26V).

However, looking just above this block in talos-evk-som.dtsi, usb_qmpphy
still uses vreg_l12a (which is configured for 1.8V):

&usb_qmpphy {
        vdda-phy-supply = <&vreg_l5a>;
        vdda-pll-supply = <&vreg_l12a>;

Similarly, ufs_mem_phy and pcie_phy also continue to use vreg_l12a for their
vdda-pll-supply.

Additionally, the sibling reference board qcs615-ride.dts leaves both
usb_qmpphy and usb_qmpphy_2 configured with vreg_l12a (1.8V).

Since supplying 1.8V to a PLL expecting 1.2V could expose the PHYs to a
significant overvoltage, or alternatively undervolt usb_qmpphy_2 if the SoC
natively requires 1.8V, should the remaining PHYs and sibling boards
be updated to the correct voltage as well?

>  
>  	status = "okay";
>  };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260803-phy-supply-fix-v1-0-5880630cde3e@oss.qualcomm.com?part=28

  reply	other threads:[~2026-08-03  7:01 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-03  6:33 [PATCH 00/28] arm64: dts: qcom: Fix swapped QMP PHY vdda-phy/vdda-pll supplies Manivannan Sadhasivam via B4 Relay
2026-08-03  6:33 ` [PATCH 01/28] dt-bindings: phy: qcom: Describe QMP USB and UFS PHY vdda-phy/vdda-pll voltages Manivannan Sadhasivam via B4 Relay
2026-08-04  8:36   ` Krzysztof Kozlowski
2026-08-03  6:34 ` [PATCH 02/28] arm64: dts: qcom: sc8280xp-blackrock: Fix swapped USB QMP PHY vdda-phy/vdda-pll supplies Manivannan Sadhasivam via B4 Relay
2026-08-03  6:44   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 03/28] arm64: dts: qcom: sa8540p: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:46   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 04/28] arm64: dts: qcom: sdm845: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:43   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 05/28] arm64: dts: qcom: sdm850: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:44   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 06/28] arm64: dts: qcom: sm8150: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:42   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 07/28] arm64: dts: qcom: sm8250: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 08/28] arm64: dts: qcom: sm8350: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:51   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 09/28] arm64: dts: qcom: sm8450: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:43   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 10/28] arm64: dts: qcom: sm8550: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:41   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 11/28] arm64: dts: qcom: qcs8550-aim300: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 12/28] arm64: dts: qcom: qcm6490: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:43   ` sashiko-bot
2026-08-04 13:24   ` Luca Weiss
2026-08-03  6:34 ` [PATCH 13/28] arm64: dts: qcom: qcs6490: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:46   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 14/28] arm64: dts: qcom: sm7225-fairphone-fp4: " Manivannan Sadhasivam via B4 Relay
2026-08-04 13:26   ` Luca Weiss
2026-08-03  6:34 ` [PATCH 15/28] arm64: dts: qcom: sc7180: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 16/28] arm64: dts: qcom: sc7280: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 17/28] arm64: dts: qcom: sc8180x: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 18/28] arm64: dts: qcom: hamoa: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:45   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 19/28] arm64: dts: qcom: purwa: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 20/28] arm64: dts: qcom: sm8650: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 21/28] arm64: dts: qcom: sm8750: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 22/28] arm64: dts: qcom: sar2130p: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 23/28] arm64: dts: qcom: kaanapali: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 24/28] arm64: dts: qcom: glymur: " Manivannan Sadhasivam via B4 Relay
2026-08-04 11:51   ` Abel Vesa
2026-08-03  6:34 ` [PATCH 25/28] arm64: dts: qcom: lemans: " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:59   ` sashiko-bot
2026-08-03  6:34 ` [PATCH 26/28] arm64: dts: qcom: eliza-mtp: " Manivannan Sadhasivam via B4 Relay
2026-08-04 11:51   ` Abel Vesa
2026-08-03  6:34 ` [PATCH 27/28] arm64: dts: qcom: sa8155p-adp: Fix swapped USB and UFS " Manivannan Sadhasivam via B4 Relay
2026-08-03  6:34 ` [PATCH 28/28] arm64: dts: qcom: talos-evk: Fix swapped USB " Manivannan Sadhasivam via B4 Relay
2026-08-03  7:01   ` sashiko-bot [this message]
2026-08-05  3:33 ` [PATCH 00/28] arm64: dts: qcom: Fix swapped " Bjorn Andersson

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=20260803070159.771841F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=manivannan.sadhasivam@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