From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: neil.armstrong@linaro.org, dmaengine@vger.kernel.org,
olteanv@gmail.com, robh@kernel.org, conor+dt@kernel.org,
Frank.Li@kernel.org, vkoul@kernel.org,
devicetree@vger.kernel.org, linux-phy@lists.infradead.org
Subject: Re: [PATCH 4/7] dt-bindings: usb: ti,musb-am33xx: Convert to DT schema
Date: Mon, 17 Aug 2026 21:58:28 +0000 [thread overview]
Message-ID: <20260817215828.978C41F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260818-ti-am33-usb-v1-4-69ac5f92df45@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] The custom vendor-specific property `mentor,ram-bits` is missing a type definition reference (`$ref`), which will cause device tree schema validation to fail.
--
--- Patch [4]: [PATCH 4/7] dt-bindings: usb: ti,musb-am33xx: Convert to DT schema ---
commit 8d75d797452b1f785af4636b0cd55212a95b505a
Author: Bhargav Joshi <j.bhargav.u@gmail.com>
dt-bindings: usb: ti,musb-am33xx: Convert to DT schema
This commit converts the TI AM33xx MUSB text bindings to DT schema format.
It includes modifications to support optional vbus interrupts and natively
supported multipoint setups, as well as adding hardware-specific properties.
> diff --git a/Documentation/devicetree/bindings/usb/ti,musb-am33xx.yaml b/Documentation/devicetree/bindings/usb/ti,musb-am33xx.yaml
> new file mode 100644
> index 0000000000000..05909d5ca3d2d
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/ti,musb-am33xx.yaml
[ ... ]
> + mentor,num-eps:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: Specifies the number of endpoints.
> + const: 16
> +
> + mentor,ram-bits:
> + description: Specifies the ram address size.
> + const: 12
[Severity: Low]
Does this property need a type definition reference?
Unlike its sibling properties (such as mentor,num-eps and mentor,power),
mentor,ram-bits is missing a $ref to a standard DT type. Because it is a
custom vendor-specific property, lacking a type reference like
$ref: /schemas/types.yaml#/definitions/uint32 typically causes
dt_binding_check to fail with a missing type definition error.
> +
> + mentor,power:
> + $ref: /schemas/types.yaml#/definitions/uint32
> + description: Controller supply capacity (in mA) when operating in host mode.
> + const: 500
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260818-ti-am33-usb-v1-0-69ac5f92df45@gmail.com?part=4
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-08-17 21:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 21:46 [PATCH 0/7] dt-bindings: usb: ti: Convert AM33xx/DA8xx MUSB bindings to DT schema Bhargav Joshi
2026-08-17 21:46 ` [PATCH 1/7] dt-bindings: dma: ti,cppi41: Convert " Bhargav Joshi
2026-08-17 21:58 ` sashiko-bot
2026-08-17 23:25 ` Bhargav Joshi
2026-08-17 21:46 ` [PATCH 2/7] dt-bindings: phy: ti,am335x-usb-phy: " Bhargav Joshi
2026-08-17 21:46 ` [PATCH 3/7] ARM: dts: ti: am335x: Fix redundant interrupts property in USB nodes Bhargav Joshi
2026-08-17 21:46 ` [PATCH 4/7] dt-bindings: usb: ti,musb-am33xx: Convert to DT schema Bhargav Joshi
2026-08-17 21:58 ` sashiko-bot [this message]
2026-08-17 23:24 ` Bhargav Joshi
2026-08-17 21:46 ` [PATCH 5/7] dt-bindings: usb: ti,am335x-usb-ctrl-module: " Bhargav Joshi
2026-08-17 21:46 ` [PATCH 6/7] dt-bindings: usb: ti,am33xx-usb: " Bhargav Joshi
2026-08-17 21:54 ` sashiko-bot
2026-08-17 23:23 ` Bhargav Joshi
2026-08-17 21:46 ` [PATCH 7/7] dt-bindings: usb: ti,da830-musb: " Bhargav Joshi
2026-08-17 22:01 ` 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=20260817215828.978C41F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=j.bhargav.u@gmail.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