All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jason Pettit" <jason.pettit@oss.qualcomm.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v4 2/3] arm64: dts: qcom: Add HP EliteBook X G2q 14 AI
Date: Mon, 17 Aug 2026 15:23:46 +0000	[thread overview]
Message-ID: <20260817152346.7F7FD1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260817-glymur-send-v4-2-3fb89cec703e@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Critical] The QMP PHY vdda-phy-supply and vdda-pll-supply regulators are swapped on all USB PHY nodes, supplying 1.2V to the 0.9V core and 0.9V to the 1.2V PLL.
--

--- Patch [2]: [PATCH v4 2/3] arm64: dts: qcom: Add HP EliteBook X G2q 14 AI ---
commit 202cffb7469000f285c774f7cd690578bdee2992
Author: Jason Pettit <jason.pettit@oss.qualcomm.com>
Subject: arm64: dts: qcom: Add HP EliteBook X G2q 14 AI

Add board support for the HP EliteBook X G2q 14" Next Gen AI PC
(Snapdragon X2 Elite / Glymur). This includes support for the internal
eDP panel, USB Type-C, chassis HDMI, USB-A host, NVMe, and other internal
peripherals.

> diff --git a/arch/arm64/boot/dts/qcom/glymur-hp-elitebook-x-g2q.dts b/arch/arm64/boot/dts/qcom/glymur-hp-elitebook-x-g2q.dts
> new file mode 100644
> index 0000000000000..7993f0e70fc00
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/glymur-hp-elitebook-x-g2q.dts
> @@ -0,0 +1,1032 @@

[ ... ]

> +&usb_0_qmpphy {
> +	vdda-phy-supply = <&vreg_l4h_e0_1p2>;
> +	vdda-pll-supply = <&vreg_l3f_e0_0p91>;
> +	refgen-supply = <&vreg_l2f_e0_0p94>;
> +
> +	status = "okay";
> +};

[Severity: Critical]
Are the regulators for the QMP PHY swapped here?

Supplying 1.2V to the 0.9V core (vdda-phy-supply) causes an overvoltage that
can physically damage the hardware.

Additionally, supplying 0.91V to the 1.2V PLL (vdda-pll-supply) means the PLL
will fail to lock, rendering the USB interface non-functional.

[ ... ]

> +&usb_1_qmpphy {
> +	vdda-phy-supply = <&vreg_l4h_e0_1p2>;
> +	vdda-pll-supply = <&vreg_l1h_e0_0p94>;
> +	refgen-supply = <&vreg_l2f_e0_0p94>;
> +
> +	status = "okay";
> +};

[Severity: Critical]
Could the regulators for this QMP PHY also be swapped?

Just like usb_0_qmpphy, it appears 1.2V is being supplied to the 0.9V core and
0.94V is being supplied to the 1.2V PLL.

[ ... ]

> +&usb_2_qmpphy {
> +	vdda-phy-supply = <&vreg_l4h_e0_1p2>;
> +	vdda-pll-supply = <&vreg_l3f_e0_0p91>;
> +	refgen-supply = <&vreg_l2f_e0_0p94>;
> +
> +	/delete-property/ mode-switch;
> +	/delete-property/ orientation-switch;
> +
> +	status = "okay";

[Severity: Critical]
Does this PHY also have the supplies swapped between the 0.9V core and
the 1.2V PLL?

[ ... ]

> +&usb_mp_qmpphy0 {
> +	vdda-phy-supply = <&vreg_l4h_e0_1p2>;
> +	vdda-pll-supply = <&vreg_l2h_e0_0p88>;
> +	refgen-supply = <&vreg_l4f_e1_1p2>;
> +
> +	status = "okay";
> +};

[Severity: Critical]
Are the supplies swapped on this PHY as well, causing an overvoltage on the
0.9V core?

[ ... ]

> +&usb_mp_qmpphy1 {
> +	vdda-phy-supply = <&vreg_l4h_e0_1p2>;
> +	vdda-pll-supply = <&vreg_l2h_e0_0p88>;
> +	refgen-supply = <&vreg_l4f_e1_1p2>;
> +
> +	status = "okay";
> +};

[Severity: Critical]
And here as well? It looks like the same swap pattern applies to all the
USB PHY nodes in this board device tree.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260817-glymur-send-v4-0-3fb89cec703e@oss.qualcomm.com?part=2

  reply	other threads:[~2026-08-17 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17 15:09 [PATCH v4 0/3] X2 Elite HP EliteBook X G2q support Jason Pettit
2026-08-17 15:09 ` [PATCH v4 1/3] dt-bindings: arm: qcom: Add HP EliteBook X G2q 14 AI Jason Pettit
2026-08-17 15:09 ` [PATCH v4 2/3] arm64: dts: " Jason Pettit
2026-08-17 15:23   ` sashiko-bot [this message]
2026-08-17 15:09 ` [PATCH v4 3/3] firmware: qcom: scm: Allow QSEECOM on " Jason Pettit

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=20260817152346.7F7FD1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jason.pettit@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 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.