From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: vkoul@kernel.org, olteanv@gmail.com, dmaengine@vger.kernel.org,
conor+dt@kernel.org, neil.armstrong@linaro.org, robh@kernel.org,
Frank.Li@kernel.org, devicetree@vger.kernel.org,
linux-phy@lists.infradead.org
Subject: Re: [PATCH v3 5/6] dt-bindings: usb: ti,am33xx-usb: Convert to DT schema
Date: Mon, 31 Aug 2026 23:32:51 +0000 [thread overview]
Message-ID: <20260831233252.06E641F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260901-ti-am33-usb-v3-5-5e15c617d2e9@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Undefined labels in the YAML example cause `dtc` compilation to fail during `make dt_binding_check`.
--
commit 8b02af2c630db204aabbcbc1828484db912830c0
Author: Bhargav Joshi <j.bhargav.u@gmail.com>
dt-bindings: usb: ti,am33xx-usb: Convert to DT schema
This commit converts the TI AM33xx USB Wrapper text binding to DT schema.
It drops the USB control module from child nodes, allows standard phy child
node names, and marks the legacy ti,hwmods property as deprecated.
> diff --git a/Documentation/devicetree/bindings/usb/ti,am33xx-usb.yaml b/Documentation/devicetree/bindings/usb/ti,am33xx-usb.yaml
> new file mode 100644
> index 0000000000000..0b36b9ddfb4a9
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/ti,am33xx-usb.yaml
[ ... ]
> +examples:
> + - |
> + usb@47400000 {
> + compatible = "ti,am33xx-usb";
> + reg = <0x47400000 0x1000>;
> + ranges;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ti,hwmods = "usb_otg_hs";
> +
> + usb-phy@47401300 {
> + compatible = "ti,am335x-usb-phy";
> + reg = <0x47401300 0x100>;
> + reg-names = "phy";
> + ti,ctrl_mod = <&ctrl_mod>;
[Severity: Low]
Does this reference to ctrl_mod cause a build failure during dtc compilation?
The control module node and its label appear to have been removed from the
example during the text-to-YAML conversion, which may result in a fatal
"Reference to non-existent node or label" error when running make
dt_binding_check.
> + #phy-cells = <0>;
> + };
> +
> + usb@47401000 {
> + compatible = "ti,musb-am33xx";
> + reg = <0x47401400 0x400>,
> + <0x47401000 0x200>;
> + reg-names = "mc", "control";
> + interrupts = <18>;
> + interrupt-names = "mc";
> + dr_mode = "otg";
> + mentor,multipoint = <1>;
> + mentor,num-eps = <16>;
> + mentor,ram-bits = <12>;
> + mentor,power = <500>;
> + phys = <&usb0_phy>;
[Severity: Low]
Will dtc compilation fail on this phandle reference? The usb0_phy label
was removed from the usb-phy@47401300 node in the example above, meaning
this reference is undefined and may break make dt_binding_check.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260901-ti-am33-usb-v3-0-5e15c617d2e9@gmail.com?part=5
--
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-31 23:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 23:23 [PATCH v3 0/6] dt-bindings: usb: ti: Convert AM33xx/DA8xx MUSB bindings to DT schema Bhargav Joshi
2026-08-31 23:23 ` [PATCH v3 1/6] dt-bindings: dma: ti,cppi41: Convert " Bhargav Joshi
2026-08-31 23:35 ` sashiko-bot
2026-08-31 23:23 ` [PATCH v3 2/6] dt-bindings: phy: ti,am335x-usb-phy: " Bhargav Joshi
2026-09-03 11:45 ` Manivannan Sadhasivam
2026-08-31 23:23 ` [PATCH v3 3/6] dt-bindings: usb: ti,musb-am33xx: " Bhargav Joshi
2026-08-31 23:34 ` sashiko-bot
2026-08-31 23:23 ` [PATCH v3 4/6] dt-bindings: usb: ti,am335x-usb-ctrl-module: " Bhargav Joshi
2026-08-31 23:32 ` sashiko-bot
2026-08-31 23:23 ` [PATCH v3 5/6] dt-bindings: usb: ti,am33xx-usb: " Bhargav Joshi
2026-08-31 23:32 ` sashiko-bot [this message]
2026-08-31 23:23 ` [PATCH v3 6/6] dt-bindings: usb: ti,da830-musb: " Bhargav Joshi
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=20260831233252.06E641F000E9@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