From: sashiko-bot@kernel.org
To: "Navid Ghahremani" <ghahramani.navid@gmail.com>
Cc: linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v2 21/24] dt-bindings: usb: Add ZTE ZX279128S DWC3 controller
Date: Thu, 15 Oct 2026 07:24:42 +0000 [thread overview]
Message-ID: <sashiko-outbox-172415@kernel.org> (raw)
In-Reply-To: <20261014072109.1759502-22-ghahramani.navid@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: usb: missing reset header and incorrect macros in example
--
commit 4b49967364799b06d338b499b3fff468b97de327
Author: Navid Ghahremani <ghahramani.navid@gmail.com>
dt-bindings: usb: Add ZTE ZX279128S DWC3 controller
Describe the USB host integration with three CRM clocks and four reset
bits.
> diff --git a/Documentation/devicetree/bindings/usb/zte,zx279128s-dwc3.yaml b/Documentation/devicetree/bindings/usb/zte,zx279128s-dwc3.yaml
> new file mode 100644
> index 0000000000000..2fd9fe0cc74bd
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/zte,zx279128s-dwc3.yaml
[ ... ]
> +examples:
> + - |
> + #include <dt-bindings/clock/zte,zx279128s-crm.h>
> + #include <dt-bindings/interrupt-controller/arm-gic.h>
> +
> + usb@9100000 {
> + compatible = "zte,zx279128s-dwc3";
> + reg = <0x09100000 0x100000>;
> + interrupts = <GIC_SPI 50 IRQ_TYPE_LEVEL_HIGH>;
> + clocks = <&topcrm ZX279128S_TOP_USB_REF>,
> + <&topcrm ZX279128S_TOP_USB_ACLK>,
> + <&topcrm ZX279128S_TOP_USB_SUSPEND>;
> + clock-names = "ref", "bus_early", "suspend";
> + resets = <&topcrm ZX279128S_TOP_RST_USB_B11>,
> + <&topcrm ZX279128S_TOP_RST_USB_B14>,
> + <&topcrm ZX279128S_TOP_RST_USB_B9>,
> + <&topcrm ZX279128S_TOP_RST_USB_B10>;
[Severity: Low]
Will this example pass make dt_binding_check?
The example is missing an include for <dt-bindings/reset/zte,zx279128s-reset.h>.
Additionally, the macros used here (e.g., ZX279128S_TOP_RST_USB_B11) appear
to be misspelled. The actual macros defined in the reset header are prefixed
with ZX279128S_RESET_ (e.g., ZX279128S_RESET_USB_B11).
This discrepancy will result in a build failure when validating the schema.
> + dr_mode = "host";
> + };
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261014072109.1759502-1-ghahramani.navid@gmail.com?part=21
next prev parent reply other threads:[~2026-10-15 7:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261014072109.1759502-1-ghahramani.navid@gmail.com>
2026-10-14 7:21 ` [PATCH v2 21/24] dt-bindings: usb: Add ZTE ZX279128S DWC3 controller Navid Ghahremani
2026-10-15 7:24 ` sashiko-bot [this message]
2026-10-14 7:21 ` [PATCH v2 22/24] usb: dwc3: generic-plat: Add ZTE ZX279128S Navid Ghahremani
2026-10-15 7:24 ` 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=sashiko-outbox-172415@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ghahramani.navid@gmail.com \
--cc=linux-usb@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