From: sashiko-bot@kernel.org
To: "Adrian Ng Ho Yin" <adrian.ho.yin.ng@altera.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/4] dt-bindings: usb: add Altera Agilex5 DWC3 controller
Date: Mon, 07 Sep 2026 08:35:57 +0000 [thread overview]
Message-ID: <20260907083558.04EB51F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <19d22389b795bd0883dc481f045a293b400f1ea3.1788757821.git.adrian.ho.yin.ng@altera.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The schema incorrectly uses `additionalProperties: false` instead of `unevaluatedProperties: false`, which negates inherited schemas and forces redundant property declarations.
--
commit 9d62a972209f1de97f540bff2202c5f7fd9c1a48
Author: Adrian Ng Ho Yin <adrian.ho.yin.ng@altera.com>
dt-bindings: usb: add Altera Agilex5 DWC3 controller
Add a binding for the Altera Agilex5 SoC integration of the Synopsys DWC3
USB controller, covering clocks, resets, PHYs, and optional IOMMU support.
> diff --git a/Documentation/devicetree/bindings/usb/altr,agilex5-dwc3.yaml b/Documentation/devicetree/bindings/usb/altr,agilex5-dwc3.yaml
> new file mode 100644
> index 0000000000000..9970d7c9d6fae
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/altr,agilex5-dwc3.yaml
[ ... ]
> + reset-names:
> + items:
> + - const: core
> + - const: ecc
> +
> + dr_mode: true
> +
> + maximum-speed: true
> +
> + snps,dis_u2_susphy_quirk: true
> +
> + snps,dis_u3_susphy_quirk: true
[Severity: Medium]
Are these property declarations necessary?
These dummy redeclarations appear to be a workaround for the
additionalProperties restriction below. Once unevaluatedProperties: false is
used instead, these can be safely removed as they will be properly inherited
from the common schema.
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> + - interrupts
> + - phys
> + - phy-names
> + - resets
> + - reset-names
> +
> +additionalProperties: false
[Severity: Medium]
Does this incorrectly reject standard properties inherited from
snps,dwc3-common.yaml?
Using additionalProperties: false instead of unevaluatedProperties: false
strictly restricts properties to only those defined in this file. This breaks
schema inheritance, meaning any standard DWC3 properties not explicitly
redefined here will cause dt_binding_check to fail.
--
Sashiko AI review · https://sashiko.dev/#/patchset/cover.1788757821.git.adrian.ho.yin.ng@altera.com?part=1
next prev parent reply other threads:[~2026-09-07 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 8:21 [PATCH v5 0/4] Add USB3.1 support for Agilex5 Adrian Ng Ho Yin
2026-09-07 8:21 ` [PATCH v5 1/4] dt-bindings: usb: add Altera Agilex5 DWC3 controller Adrian Ng Ho Yin
2026-09-07 8:35 ` sashiko-bot [this message]
2026-09-07 16:59 ` Conor Dooley
2026-09-08 6:01 ` NG, ADRIAN HO YIN
2026-09-08 16:47 ` Conor Dooley
2026-09-07 8:21 ` [PATCH v5 2/4] arm64: dts: intel: agilex5: add USB3.1 controller node Adrian Ng Ho Yin
2026-09-07 8:44 ` sashiko-bot
2026-09-07 8:21 ` [PATCH v5 3/4] arm64: dts: intel: agilex5: remove usb0 in Agilex5 SoCDK Adrian Ng Ho Yin
2026-09-07 8:21 ` [PATCH v5 4/4] usb: dwc3: add Altera Agilex5 support to generic platform driver Adrian Ng Ho Yin
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=20260907083558.04EB51F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=adrian.ho.yin.ng@altera.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