From: sashiko-bot@kernel.org
To: "George Moussalem" <george.moussalem@outlook.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 10/10] arm64: dts: qcom: ipq9574: Flatten usb controller node
Date: Sun, 06 Sep 2026 04:08:52 +0000 [thread overview]
Message-ID: <20260906040853.309AA1F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260906-ipq-flatten-usb-v2-10-dab83120b10a@outlook.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Devicetree Schema Violation: Incorrect ordering of `interrupt-names` for `qcom,snps-dwc3`.
--
commit 83a48e27af172a1417a53f107382ebfe032982cc
Author: George Moussalem <george.moussalem@outlook.com>
arm64: dts: qcom: ipq9574: Flatten usb controller node
Flatten usb controller nodes and update to using latest bindings and
flattened driver approach.
> diff --git a/arch/arm64/boot/dts/qcom/ipq9574.dtsi b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> index 5a5bda5f21a11..cf2eacb16c360 100644
> --- a/arch/arm64/boot/dts/qcom/ipq9574.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq9574.dtsi
[ ... ]
> @@ -780,32 +777,29 @@ usb3: usb@8af8800 {
> assigned-clock-rates = <200000000>,
> <24000000>;
>
> - interrupts-extended = <&intc GIC_SPI 134 IRQ_TYPE_LEVEL_HIGH>,
> + interrupts-extended = <&intc GIC_SPI 140 IRQ_TYPE_LEVEL_HIGH>,
> + <&intc GIC_SPI 134 IRQ_TYPE_LEVEL_HIGH>,
> <&intc GIC_SPI 136 IRQ_TYPE_LEVEL_HIGH>,
> <&intc GIC_SPI 111 IRQ_TYPE_LEVEL_HIGH>,
> <&intc GIC_SPI 112 IRQ_TYPE_LEVEL_HIGH>;
> - interrupt-names = "pwr_event",
> + interrupt-names = "dwc_usb3",
> + "pwr_event",
> "qusb2_phy",
> "dm_hs_phy_irq",
> "dp_hs_phy_irq";
[Severity: Low]
Will this ordering cause a dtbs_check validation failure?
The qcom,snps-dwc3.yaml binding strictly requires the interrupt names for
qcom,ipq9574-dwc3 to follow an exact order: dwc_usb3, pwr_event, qusb2_phy,
dp_hs_phy_irq, and dm_hs_phy_irq.
Here in usb3: usb@8a00000, dm_hs_phy_irq appears before dp_hs_phy_irq, which
preserves the legacy ordering instead of matching the updated binding.
Could the interrupt-names and their corresponding interrupts-extended mappings
be swapped to match the schema?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260906-ipq-flatten-usb-v2-0-dab83120b10a@outlook.com?part=10
next prev parent reply other threads:[~2026-09-06 4:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-06 3:52 [PATCH v2 00/10] Flatten USB Controller Nodes on IPQ SoCs George Moussalem via B4 Relay
2026-09-06 3:52 ` [PATCH v2 01/10] usb: dwc3: core: Allow glue layer to pass reference clock rate George Moussalem via B4 Relay
2026-09-07 4:02 ` Varadarajan Narayanan
2026-09-06 3:52 ` [PATCH v2 02/10] usb: dwc3: qcom: Add support for selecting UTMI as reference clock George Moussalem via B4 Relay
2026-09-07 4:03 ` Varadarajan Narayanan
2026-09-06 3:52 ` [PATCH v2 03/10] arm64: dts: qcom: ipq5018: Flatten usb controller node George Moussalem via B4 Relay
2026-09-06 3:52 ` [PATCH v2 04/10] arm64: dts: qcom: ipq5332: " George Moussalem via B4 Relay
2026-09-06 3:52 ` [PATCH v2 05/10] arm64: dts: qcom: ipq5424: Flatten usb controller nodes George Moussalem via B4 Relay
2026-09-06 3:52 ` [PATCH v2 06/10] arm64: dts: qcom: ipq6018: move DR mode to board DTS George Moussalem via B4 Relay
2026-09-06 3:52 ` [PATCH v2 07/10] arm64: dts: qcom: ipq6018: Flatten usb controller nodes George Moussalem via B4 Relay
2026-09-06 4:01 ` sashiko-bot
2026-09-06 3:52 ` [PATCH v2 08/10] arm64: dts: qcom: ipq8074: move DR mode to board DTS George Moussalem via B4 Relay
2026-09-06 3:52 ` [PATCH v2 09/10] arm64: dts: qcom: ipq8074: Flatten usb controller nodes George Moussalem via B4 Relay
2026-09-06 3:52 ` [PATCH v2 10/10] arm64: dts: qcom: ipq9574: Flatten usb controller node George Moussalem via B4 Relay
2026-09-06 4:08 ` sashiko-bot [this message]
2026-09-06 4:30 ` [PATCH v2 00/10] Flatten USB Controller Nodes on IPQ SoCs George Moussalem
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=20260906040853.309AA1F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=george.moussalem@outlook.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