Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "George Moussalem" <george.moussalem@outlook.com>
Cc: vkoul@kernel.org, linux-phy@lists.infradead.org, robh@kernel.org,
	olteanv@gmail.com, neil.armstrong@linaro.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 11/14] arm64: dts: qcom: ipq5018: Add Super-Speed UNIPHY to USB node
Date: Wed, 12 Aug 2026 09:57:46 +0000	[thread overview]
Message-ID: <20260812095747.3631D1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260812-ipq5018-usb3-v2-11-8f355d7ff0ef@outlook.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] Removing `qcom,select-utmi-as-pipe-clk` from the base `.dtsi` breaks USB initialization on boards that do not enable `usbphy1` (USB 2.0-only configurations).
--

--- Patch [11]: [PATCH v2 11/14] arm64: dts: qcom: ipq5018: Add Super-Speed UNIPHY to USB node ---
commit cad428ffac4e6a077748bf0a342a5d6933fea31b
Author: George Moussalem <george.moussalem@outlook.com>

arm64: dts: qcom: ipq5018: Add Super-Speed UNIPHY to USB node

This commit adds the USB3 UNIPHY node to the USB controller node in the
IPQ5018 device tree. It also removes the property that selects the UTMI
clock as the pipe clock, expecting the pipe clock to be supplied by the
USB3 UNIPHY instead.

> diff --git a/arch/arm64/boot/dts/qcom/ipq5018.dtsi b/arch/arm64/boot/dts/qcom/ipq5018.dtsi
> index 82e9ba6020ebd..87c3ade70217f 100644
> --- a/arch/arm64/boot/dts/qcom/ipq5018.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq5018.dtsi
> @@ -618,10 +618,8 @@ usb: usb@8a00000 {
>  
>  			resets = <&gcc GCC_USB0_BCR>;
>  
> -			phys = <&usbphy0>;
> -			phy-names = "usb2-phy";
> -
> -			qcom,select-utmi-as-pipe-clk;

[Severity: High]
Will removing this property break boards that do not enable usbphy1?

For example, looking at arch/arm64/boot/dts/qcom/ipq5018-rdp432-c2.dts,
it configures USB but lacks usbphy1:

&usb {
        dr_mode = "host";

        status = "okay";
};

Because qcom,select-utmi-as-pipe-clk is no longer in the base device tree,
the dwc3-qcom wrapper won't fall back to the UTMI clock.

Since usbphy1 is disabled on these USB 2.0-only configurations, the PHY
driver doesn't probe and the pipe clock is never provided. Does this cause
the dwc3 controller to hang while waiting for a non-existent clock during
initialization?

> +			phys = <&usbphy0>, <&usbphy1>;
> +			phy-names = "usb2-phy", "usb3-phy";
>  
>  			tx-fifo-resize;
>  			snps,is-utmi-l1-suspend;

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260812-ipq5018-usb3-v2-0-8f355d7ff0ef@outlook.com?part=11

  reply	other threads:[~2026-08-12  9:57 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-12  9:34 [PATCH v2 00/14] Enable USB3 for Qualcomm IPQ5018 and IPQ5332 George Moussalem via B4 Relay
2026-08-12  9:34 ` [PATCH v2 01/14] dt-bindings: phy: Document the Qualcomm IPQ5332 UNIPHY USB Super-speed PHY George Moussalem via B4 Relay
2026-08-12  9:41   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 02/14] phy: qcom: Introduce Qualcomm IPQ5332 Super-Speed USB UNIPHY driver George Moussalem via B4 Relay
2026-08-12  9:48   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 03/14] arm64: dts: qcom: ipq5018: Add USB Super-Speed PHY node George Moussalem via B4 Relay
2026-08-12  9:51   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 04/14] arm64: dts: qcom: ipq5332: Flatten usb controller node George Moussalem via B4 Relay
2026-08-12 10:25   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 05/14] arm64: dts: qcom: ipq5018: " George Moussalem via B4 Relay
2026-08-12  9:56   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 06/14] dt-bindings: usb: qcom,snps-dwc3: Add clocks for USB3 on Qualcomm IPQ5332 George Moussalem via B4 Relay
2026-08-12  9:46   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 07/14] dt-bindings: usb: qcom,snps-dwc3: Add clocks for USB3 on Qualcomm IPQ5018 George Moussalem via B4 Relay
2026-08-12  9:51   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 08/14] arm64: dts: qcom: ipq5332: Add clocks required for USB3 support George Moussalem via B4 Relay
2026-08-12  9:34 ` [PATCH v2 09/14] arm64: dts: qcom: ipq5018: " George Moussalem via B4 Relay
2026-08-12  9:48   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 10/14] arm64: dts: qcom: ipq5332: Add Super-Speed UNIPHY to USB node George Moussalem via B4 Relay
2026-08-12  9:55   ` sashiko-bot
2026-08-12 10:56   ` Sergey Shtylyov
2026-08-12  9:34 ` [PATCH v2 11/14] arm64: dts: qcom: ipq5018: " George Moussalem via B4 Relay
2026-08-12  9:57   ` sashiko-bot [this message]
2026-08-12 10:57   ` Sergey Shtylyov
2026-08-12  9:34 ` [PATCH v2 12/14] arm64: dts: qcom: ipq5332: Enable USB Super-Speed PHY George Moussalem via B4 Relay
2026-08-12  9:54   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 13/14] arm64: dts: qcom: ipq5018: " George Moussalem via B4 Relay
2026-08-12  9:57   ` sashiko-bot
2026-08-12  9:34 ` [PATCH v2 14/14] arm64: defconfig: Enable qcom USB UNIPHY driver George Moussalem via B4 Relay

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=20260812095747.3631D1F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=george.moussalem@outlook.com \
    --cc=linux-phy@lists.infradead.org \
    --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