From: sashiko-bot@kernel.org
To: "Varadarajan Narayanan" <varadarajan.narayanan@oss.qualcomm.com>
Cc: krzk+dt@kernel.org, linux-phy@lists.infradead.org,
robh@kernel.org, devicetree@vger.kernel.org, vkoul@kernel.org,
neil.armstrong@linaro.org, conor+dt@kernel.org,
olteanv@gmail.com
Subject: Re: [PATCH 3/5] dt-bindings: usb: qcom,dwc3: Add ipq5210 to USB DWC3 bindings
Date: Fri, 15 May 2026 11:18:26 +0000 [thread overview]
Message-ID: <20260515111826.F1623C2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260515-usb2phy-v1-3-5f8338d466bf@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The new compatible string `qcom,ipq5210-dwc3` is added to the top-level `compatible` list but is omitted from the `allOf` conditional blocks that enforce device-specific constraints.
--
commit f7f00d62e8a27abcab7835184425ce9a31f1b2c3
Author: Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>
dt-bindings: usb: qcom,dwc3: Add ipq5210 to USB DWC3 bindings
Update dt-bindings to add ipq5210 to USB DWC3 controller list.
> diff --git a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> index a7f58114c02e8..f8e0819be894b 100644
> --- a/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> +++ b/Documentation/devicetree/bindings/usb/qcom,dwc3.yaml
> @@ -26,6 +26,7 @@ properties:
> - enum:
> - qcom,ipq4019-dwc3
> - qcom,ipq5018-dwc3
> + - qcom,ipq5210-dwc3
Should this new compatible string also be added to the allOf conditional blocks
that enforce constraints for related hardware?
Similar generations like ipq5018 and ipq5332 enforce clock and interrupt
limits further down in the file:
allOf:
- if:
properties:
compatible:
contains:
enum:
- qcom,ipq5018-dwc3
- qcom,ipq5332-dwc3
then:
properties:
interrupts:
maxItems: 3
Does ipq5210 share these constraints, and should it be added to the appropriate
conditionals?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260515-usb2phy-v1-0-5f8338d466bf@oss.qualcomm.com?part=3
next prev parent reply other threads:[~2026-05-15 11:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 10:47 [PATCH 0/5] Enable ipq5210 USB support Varadarajan Narayanan
2026-05-15 10:47 ` [PATCH 1/5] dt-bindings: phy: qcom,qusb2: Document ipq5210 compatible Varadarajan Narayanan
2026-05-15 10:47 ` [PATCH 2/5] dt-bindings: phy: qcom,qmp-usb: Add ipq5210 USB3 PHY Varadarajan Narayanan
2026-05-15 11:13 ` sashiko-bot
2026-05-15 10:47 ` [PATCH 3/5] dt-bindings: usb: qcom,dwc3: Add ipq5210 to USB DWC3 bindings Varadarajan Narayanan
2026-05-15 11:05 ` Krzysztof Kozlowski
2026-05-15 11:18 ` sashiko-bot [this message]
2026-05-15 10:47 ` [PATCH 4/5] phy: qcom: qmp: Enable ipq5210 support Varadarajan Narayanan
2026-05-15 11:29 ` Konrad Dybcio
2026-05-15 10:47 ` [PATCH 5/5] phy: qcom-qusb2: add QUSB2 support for ipq5210 Varadarajan Narayanan
2026-05-15 11:28 ` sashiko-bot
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=20260515111826.F1623C2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--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=varadarajan.narayanan@oss.qualcomm.com \
--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