From: Conor Dooley <conor@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: marius.cristea@microchip.com, robh@kernel.org,
krzk+dt@kernel.org, devicetree@vger.kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: iio: adc: add support for PAC1944
Date: Fri, 15 May 2026 18:24:30 +0100 [thread overview]
Message-ID: <20260515-rupture-humped-772e7e2072c9@spud> (raw)
In-Reply-To: <20260515093849.4E62CC2BCB0@smtp.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2381 bytes --]
On Fri, May 15, 2026 at 09:38:47AM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Medium] The binding defines GPIO controller capabilities but omits `gpio-controller` and `#gpio-cells` from the `required` list and `examples` block.
> --
>
> commit a57d647e4dad8345f6c818b69281dba50b43a7f4
> Author: Marius Cristea <marius.cristea@microchip.com>
>
> dt-bindings: iio: adc: add support for PAC1944
>
> This commit introduces the device tree schema for the Microchip PAC194X
> and PAC195X series of Power Monitors with Accumulator. It covers variants
> for high-side and low-side current sensing or floating VBUS applications.
>
> > diff --git a/Documentation/devicetree/bindings/iio/adc/microchip,pac1944.yaml b/Documentation/devicetree/bindings/iio/adc/microchip,pac1944.yaml
> > new file mode 100644
> > index 0000000000000..eca1b25f038be
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/adc/microchip,pac1944.yaml
> [ ... ]
> > +required:
> > + - compatible
> > + - reg
> > + - vdd-supply
> > + - "#address-cells"
> > + - "#size-cells"
>
> Should `gpio-controller` and `#gpio-cells` be added to this `required` list?
>
> According to the dt-bindings guidelines, when a binding defines hardware
> provider capabilities such as a GPIO controller, the standard properties
> should be explicitly required to prevent incomplete device tree nodes from
> passing schema validation.
Same here as the other series, bot is not capable of deducing that
interrupts and gpio use have some mutual exclusion.
>
> [ ... ]
> > +examples:
> > + - |
> > + i2c {
> > + #address-cells = <1>;
> > + #size-cells = <0>;
> > +
> > + power-monitor@10 {
> > + compatible = "microchip,pac1954";
> > + reg = <0x10>;
> > + vdd-supply = <&vdd>;
> > +
> > + #address-cells = <1>;
> > + #size-cells = <0>;
>
> Should `gpio-controller` and `#gpio-cells` also be included in this example
> block?
>
> If they are added to the required properties list, omitting them from the
> examples section might cause dt_binding_check to fail.
>
> --
> Sashiko AI review · https://sashiko.dev/#/patchset/20260515092946.10791-1-marius.cristea@microchip.com?part=1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2026-05-15 17:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 9:29 [PATCH v4 0/2] add support for Microchip PAC194X Power Monitor marius.cristea
2026-05-15 9:29 ` [PATCH v4 1/2] dt-bindings: iio: adc: add support for PAC1944 marius.cristea
2026-05-15 9:38 ` sashiko-bot
2026-05-15 17:24 ` Conor Dooley [this message]
2026-05-15 17:29 ` Conor Dooley
2026-05-15 9:29 ` [PATCH v4 2/2] iio: adc: add support for PAC194X marius.cristea
2026-05-15 10:06 ` 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=20260515-rupture-humped-772e7e2072c9@spud \
--to=conor@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=marius.cristea@microchip.com \
--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