From: sashiko-bot@kernel.org
To: "Maxim Storetvedt" <mstoretv@cern.ch>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v8 3/3] arm64: dts: qcom: Add hamoa Samsung Galaxy Book4 Edge devicetrees
Date: Wed, 30 Sep 2026 21:38:26 +0000 [thread overview]
Message-ID: <20260930213826.C874F1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260930212421.4810-4-mstoretv@cern.ch>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [High] dts: swapped voltage regulators for USB QMP PHY nodes
- [Medium] dts: invalid power topology supplying 3.3V switch from 1.8V source
--
commit e084aaae679956c0579caf519602293f9f79b553
Author: Maxim Storetvedt <mstoretv@cern.ch>
Subject: arm64: dts: qcom: Add hamoa Samsung Galaxy Book4 Edge devicetrees
Adds devicetrees for the 14-inch and 16-inch hamoa SKUs of the Samsung
Galaxy Book4 Edge based on a common dtsi.
Link: https://lore.kernel.org/all/p3mhtj2rp6y2ezuwpd2gu7dwx5cbckfu4s4pazcudi4j2wogtr@4yecb2bkeyms/
Link: https://lore.kernel.org/all/20260629154812.9066-1-mail@etehtsea.me/
> diff --git a/arch/arm64/boot/dts/qcom/x1-samsung-galaxy-book4-edge.dtsi b/arch/arm64/boot/dts/qcom/x1-samsung-galaxy-book4-edge.dtsi
> new file mode 100644
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/x1-samsung-galaxy-book4-edge.dtsi
[ ... ]
> + vreg_display_vdd: regulator-display-vdd {
> + compatible = "regulator-fixed";
> +
> + regulator-name = "VREG_DISPLAY_VDD";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> +
> + gpio = <&tlmm 120 GPIO_ACTIVE_HIGH>;
> + enable-active-high;
> +
> + pinctrl-0 = <&display_vdd_en>;
> + pinctrl-names = "default";
> +
> + startup-delay-us = <400000>;
> + regulator-enable-ramp-delay = <400000>;
> +
> + vin-supply = <&vreg_octa_vdd>;
[Severity: Medium]
Is it expected that this 3.3V regulator uses a 1.8V input supply?
Looking at the definition of vreg_octa_vdd in this file, it is fixed at
1.8V. A 3.3V switch or LDO fed by a 1.8V source will cause the regulator
core to flag a 'supply voltage too low' or unsupportable constraints error
during probe when attempting to resolve the display voltage.
> +
> + regulator-always-on;
> + regulator-boot-on;
> + };
[ ... ]
> +&usb_1_ss0_qmpphy {
> + vdda-phy-supply = <&vreg_l2j_1p2>;
> + vdda-pll-supply = <&vreg_l1j_0p8>;
[Severity: High]
Could these voltage supplies be swapped?
The 1.2V supply (&vreg_l2j_1p2) is assigned to the 0.8V PHY core rail
(vdda-phy-supply), while the 0.8V supply (&vreg_l1j_0p8) is assigned to the
1.2V PLL rail (vdda-pll-supply).
During device probe, this swapped regulator assignment will activate,
causing a significant overvoltage on the PHY core and undervoltage on the
PLL, which could lead to hardware damage or initialization failures.
> +
> + status = "okay";
> +};
[ ... ]
> +&usb_1_ss1_qmpphy {
> + vdda-phy-supply = <&vreg_l2j_1p2>;
> + vdda-pll-supply = <&vreg_l2d_0p9>;
[Severity: High]
Does this node also swap the voltage supplies?
Similar to &usb_1_ss0_qmpphy above, a 1.2V supply is incorrectly assigned
to the 0.9V PHY core rail.
> +
> + status = "okay";
> +};
[ ... ]
> +&usb_1_ss2_qmpphy {
> + vdda-phy-supply = <&vreg_l2j_1p2>;
> + vdda-pll-supply = <&vreg_l2d_0p9>;
[Severity: High]
Does this node also swap the voltage supplies?
Similar to the earlier QMP PHY nodes, a 1.2V supply is incorrectly assigned
to the 0.9V PHY core rail here as well.
> +
> + /delete-property/ mode-switch;
[ ... ]
> +&usb_mp_qmpphy0 {
> + vdda-phy-supply = <&vreg_l3e_1p2>;
> + vdda-pll-supply = <&vreg_l3c_0p8>;
[Severity: High]
Does this node also swap the voltage supplies?
A 1.2V supply is incorrectly assigned to the 0.8V PHY core rail here as
well.
> +
> + status = "okay";
> +};
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260930212421.4810-1-mstoretv@cern.ch?part=3
next prev parent reply other threads:[~2026-09-30 21:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 21:24 [PATCH v8 0/3] Add initial DTS for Samsung Galaxy Book4 Edge Maxim Storetvedt
2026-09-30 21:24 ` [PATCH v8 1/3] dt-bindings: arm: Add " Maxim Storetvedt
2026-10-02 8:31 ` Krzysztof Kozlowski
2026-10-02 9:14 ` Maxim Storetvedt
2026-09-30 21:24 ` [PATCH v8 2/3] firmware: qcom: scm: Allow QSEECOM on the " Maxim Storetvedt
2026-09-30 21:24 ` [PATCH v8 3/3] arm64: dts: qcom: Add hamoa Samsung Galaxy Book4 Edge devicetrees Maxim Storetvedt
2026-09-30 21:38 ` sashiko-bot [this message]
2026-09-30 21:39 ` Antheas Kapenekakis
2026-10-01 9:04 ` Maxim Storetvedt
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=20260930213826.C874F1F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=mstoretv@cern.ch \
--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;
as well as URLs for NNTP newsgroup(s).