From: sashiko-bot@kernel.org
To: "Bjorn Andersson" <bjorn.andersson@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 2/3] arm64: dts: qcom: glymur: Add Asus Zenbook A14 (UX3407NA)
Date: Wed, 16 Sep 2026 02:05:03 +0000 [thread overview]
Message-ID: <20260916020504.060861F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260915-zenbook-dts-v2-2-41de8669a7a8@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] dts: copy-paste error leaves second USB MP PHY and redriver enabled
--
commit 0d6d4b3a24e525ee48e9f58d17b7e42d0de45fa5
Author: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
arm64: dts: qcom: glymur: Add Asus Zenbook A14 (UX3407NA)
This commit adds device tree support for the Asus Zenbook A14 (UX3407NA)
variant built on the Qualcomm Glymur platform. It introduces the base
hardware description, including the X2 Elite SoC, storage, display,
and USB connectivity.
> diff --git a/arch/arm64/boot/dts/qcom/glymur-asus-zenbook-a14-ux3407na.dts b/arch/arm64/boot/dts/qcom/glymur-asus-zenbook-a14-ux3407na.dts
> new file mode 100644
> index 0000000000000..e96e65a0c5b49
> --- /dev/null
> +++ b/arch/arm64/boot/dts/qcom/glymur-asus-zenbook-a14-ux3407na.dts
[ ... ]
> +&i2c5 {
> + clock-frequency = <400000>;
> +
> + status = "okay";
> +
> + ptn3222_1: redriver@43 {
> + compatible = "nxp,ptn3222";
> + reg = <0x43>;
> +
> + reset-gpios = <&tlmm 184 GPIO_ACTIVE_LOW>;
> +
> + vdd3v3-supply = <&vreg_l8b0>;
> + vdd1v8-supply = <&vreg_l15b0>;
> +
> + #phy-cells = <0>;
> + };
[Severity: Medium]
The commit message explicitly states the device has "one USB Type-A" and
makes no mention of an SD card reader. Does this hardware actually have a
second redriver, or is ptn3222_1 a leftover from another model's configuration?
If this hardware does not exist on the board, the kernel will attempt to probe
a non-existent I2C redriver which can cause boot probe errors.
[ ... ]
> +&usb_mp_hsphy1 {
> + vdd-supply = <&vreg_l2h0>;
> + vdda12-supply = <&vreg_l4h0>;
> +
> + phys = <&ptn3222_1>;
> +
> + status = "okay";
> +};
[Severity: Medium]
The second Multi-Port PHY is fully enabled here, which directly contradicts
the commit message's claim of a single Type-A port.
Could enabling this second PHY waste power and cause initialization errors by
attempting to bring up non-existent hardware on the boot path?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260915-zenbook-dts-v2-0-41de8669a7a8@oss.qualcomm.com?part=2
next prev parent reply other threads:[~2026-09-16 2:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 1:54 [PATCH v2 0/3] arm64: dts: qcom: Introduce Asus Zenbook A14 (UX3407NA) Bjorn Andersson
2026-09-16 1:54 ` [PATCH v2 1/3] dt-bindings: arm: qcom: Add " Bjorn Andersson
2026-09-16 1:54 ` [PATCH v2 2/3] arm64: dts: qcom: glymur: " Bjorn Andersson
2026-09-16 2:05 ` sashiko-bot [this message]
2026-09-16 10:42 ` Abel Vesa
2026-09-16 12:29 ` Konrad Dybcio
2026-09-16 1:54 ` [PATCH v2 3/3] firmware: qcom: scm: Allow QSEECOM on " Bjorn Andersson
2026-09-16 10:40 ` Abel Vesa
2026-09-16 22:31 ` (subset) [PATCH v2 0/3] arm64: dts: qcom: Introduce " 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=20260916020504.060861F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--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