Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: sashiko-bot@kernel.org
Cc: Alexandre Hamamdjian via B4 Relay
	<devnull+azkali.limited.gmail.com@kernel.org>,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v2 2/3] dt-bindings: usb: add Rohm BM92TXX Type-C controller
Date: Tue, 12 May 2026 17:49:18 +0100	[thread overview]
Message-ID: <20260512-sighing-riverside-d9a1aa21a385@spud> (raw)
In-Reply-To: <20260511220506.C54B0C2BCB0@smtp.kernel.org>

[-- Attachment #1: Type: text/plain, Size: 2641 bytes --]

On Mon, May 11, 2026 at 10:05:06PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
> - [Low] Missing type definitions and non-standard unit suffix for `rohm,pd-*v-current-limit-ma`.
> - [Low] Invalid Devicetree property naming with underscores (`pd_bat_chg-supply`).
> - [Low] Use of deprecated singular GPIO property suffix (`rohm,vconn-en-gpio`).
> --
> 
> commit 482fd67d1e5e9ceafc592495c4e2a23d21e35b0e
> Author: Alexandre Hamamdjian <azkali.limited@gmail.com>
> 
> dt-bindings: usb: add Rohm BM92TXX Type-C controller
> 
> Add the device-tree binding documentation for the Rohm BM92TXX family
> of USB Type-C and Power Delivery controllers.
> 
> > diff --git a/Documentation/devicetree/bindings/usb/rohm,bm92t.yaml b/Documentation/devicetree/bindings/usb/rohm,bm92t.yaml
> > new file mode 100644
> > index 0000000000000..007f70a8f5bb1
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/usb/rohm,bm92t.yaml
> 
> [ ... ]
> 
> > +  vbus-source-supply:
> > +    description: VBUS source (provider) regulator.
> > +
> > +  pd_bat_chg-supply:
> > +    description: Battery charger regulator gated by Power Delivery state.
> 
> Does this property name violate Devicetree naming conventions? Devicetree
> properties typically use hyphens instead of underscores (e.g.,
> pd-bat-chg-supply).
> 
> > +
> > +  rohm,vconn-en-gpio:
> > +    maxItems: 1
> > +    description: GPIO controlling the external VCONN switch.
> 
> Should this property use the standard -gpios suffix? Even for a single GPIO
> line, the standard suffix is -gpios rather than the deprecated -gpio.
> 
> [ ... ]
> 
> > +  rohm,dock-power-limit-disable:
> > +    type: boolean
> > +    description:
> > +      Disable the lower power limit applied when a dock is detected.
> > +
> > +  rohm,pd-5v-current-limit-ma:
> > +    description: Charging current limit in mA when 5V PD contract is active.
> 
> Does this property lack an explicit type definition? Custom properties without
> standard unit suffixes require a type reference, otherwise schema validation
> will fail for integer array values. Also, the -ma suffix is not a standard
> unit suffix (such as -milliamp or -microamp).
> 
> I see this schema validation failure is fixed later in the series by commit
> 315ea48f16e75d9fc77bc6e2af87cacc47b7249f ("dt-bindings: usb: fix properties
> type").

Properly suffixed properties should be used instead of making some up,
but also patches in a series that fix issues introduced by a series
should always be squashed..

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2026-05-12 16:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-10 18:32 [PATCH v2 0/3] usb: typec: add Rohm BM92TXX Type-C / PD controller driver Alexandre Hamamdjian via B4 Relay
2026-05-10 18:32 ` [PATCH v2 1/3] usb: typec: bm92txx: add Rohm BM92TXX support Alexandre Hamamdjian via B4 Relay
2026-05-11 11:07   ` Bartosz Golaszewski
2026-05-11 14:57   ` Heikki Krogerus
2026-05-11 21:55   ` sashiko-bot
2026-05-10 18:32 ` [PATCH v2 2/3] dt-bindings: usb: add Rohm BM92TXX Type-C controller Alexandre Hamamdjian via B4 Relay
2026-05-10 19:46   ` Rob Herring (Arm)
2026-05-11 12:35     ` Rob Herring
2026-05-11 22:05   ` sashiko-bot
2026-05-12 16:49     ` Conor Dooley [this message]
2026-05-10 18:32 ` [PATCH v2 3/3] dt-bindings: usb: fix properties type Alexandre Hamamdjian via B4 Relay

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=20260512-sighing-riverside-d9a1aa21a385@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+azkali.limited.gmail.com@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-bot@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