Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Bhargav Joshi" <j.bhargav.u@gmail.com>
Cc: conor+dt@kernel.org, robh@kernel.org, vkoul@kernel.org,
	dmaengine@vger.kernel.org, neil.armstrong@linaro.org,
	Frank.Li@kernel.org, linux-phy@lists.infradead.org,
	olteanv@gmail.com, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 4/6] dt-bindings: usb: ti,am335x-usb-ctrl-module: Convert to DT schema
Date: Mon, 31 Aug 2026 23:32:15 +0000	[thread overview]
Message-ID: <20260831233215.E43E41F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260901-ti-am33-usb-v3-4-5e15c617d2e9@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Documentation loss for `reg` property entries during dt-schema conversion.
--

commit c1a1061abb654fbffdeb37f5a8ae9d8c5c5596f0
Author: Bhargav Joshi <j.bhargav.u@gmail.com>

dt-bindings: usb: ti,am335x-usb-ctrl-module: Convert to DT schema

Convert the TI AM335x USB Control Module text bindings to DT schema. No
functional changes.

> diff --git a/Documentation/devicetree/bindings/usb/am33xx-usb.txt b/Documentation/devicetree/bindings/usb/am33xx-usb.txt
> index 5973f88bcc65d..94312ad8ec8cd 100644
> --- a/Documentation/devicetree/bindings/usb/am33xx-usb.txt
> +++ b/Documentation/devicetree/bindings/usb/am33xx-usb.txt
> @@ -8,15 +8,6 @@ The glue layer contains multiple child nodes. It is required to have
>  at least a control module node, USB node and a PHY node. The second USB
>  node and its PHY node are optional. The DMA node is also optional.
>  
> -Reset module
> -~~~~~~~~~~~~
> -- compatible: ti,am335x-usb-ctrl-module
> -- reg: offset and length of the "USB control registers" in the "Control
> -  Module" block. A second offset and length for the USB wake up control
> -  in the same memory block.
> -- reg-names: "phy_ctrl" for the "USB control registers" and "wakeup" for
> -  the USB wake up control register.
> -

[ ... ]

> diff --git a/Documentation/devicetree/bindings/usb/ti,am335x-usb-ctrl-module.yaml b/Documentation/devicetree/bindings/usb/ti,am335x-usb-ctrl-module.yaml
> new file mode 100644
> index 0000000000000..f8ac0af745c6c
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/usb/ti,am335x-usb-ctrl-module.yaml
> @@ -0,0 +1,38 @@

[ ... ]

> +properties:
> +  compatible:
> +    const: ti,am335x-usb-ctrl-module
> +
> +  reg:
> +    maxItems: 2

[Severity: Low]
Does this YAML conversion lose some of the documentation details from the
original text binding?

The previous text binding included explicit descriptions for the two reg
entries ("USB control registers" and "USB wake up control"). While reg-names
are provided below, should an items list under reg be included to preserve
these explicit descriptions?

> +
> +  reg-names:
> +    items:
> +      - const: phy_ctrl
> +      - const: wakeup

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260901-ti-am33-usb-v3-0-5e15c617d2e9@gmail.com?part=4

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

  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 [this message]
2026-08-31 23:23 ` [PATCH v3 5/6] dt-bindings: usb: ti,am33xx-usb: " Bhargav Joshi
2026-08-31 23:32   ` sashiko-bot
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=20260831233215.E43E41F000E9@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