Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: Radu Sabau via B4 Relay
	<devnull+radu.sabau.analog.com@kernel.org>,
	conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v12 1/6] dt-bindings: iio: adc: add AD4691 family
Date: Tue, 19 May 2026 18:26:06 +0100	[thread overview]
Message-ID: <20260519-bamboo-gleeful-669dcbefb0a3@spud> (raw)
In-Reply-To: <20260519122832.780DCC2BCB3@smtp.kernel.org>

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

On Tue, May 19, 2026 at 12:28:32PM +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.
> --
> 
> commit 96f168db5f8432c094e1917f0e5c69f84e070941
> Author: Radu Sabau <radu.sabau@analog.com>
> 
> dt-bindings: iio: adc: add AD4691 family
> 
> This commit adds device tree bindings for the Analog Devices AD4691 family
> of multichannel SAR ADCs. It describes the hardware connections including
> power domains, optional PWM for CNV Burst Mode, reset GPIO, and GP pins
> usable as interrupts or GPIOs.
> 
> > diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad4691.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad4691.yaml
> > new file mode 100644
> > index 0000000000000..af28a0c1cfa9e
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad4691.yaml
> [ ... ]
> > +  gpio-controller: true
> > +
> > +  '#gpio-cells':
> > +    const: 2
> > +
> > +  '#trigger-source-cells':
> > +    description:
> > +      This node can act as a trigger source. The single cell in a consumer
> > +      reference specifies the GP pin number (0-3) used as the trigger output.
> > +    const: 1
> > +
> > +required:
> > +  - compatible
> > +  - reg
> > +  - avdd-supply
> > +  - vio-supply
> 
> Should gpio-controller and #gpio-cells be added to the required list here?
> 
> When a hardware variant provides GPIO controller capabilities, these
> properties generally need to appear in the required list.

More deja vu. This is incorrect advice, reading the binding or commit
message explains it, and is being regurgitated on multiple versions.

Fix this please.

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

  reply	other threads:[~2026-05-19 17:26 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-19 12:20 [PATCH v12 0/6] iio: adc: ad4691: add driver for AD4691 multichannel SAR ADC family Radu Sabau via B4 Relay
2026-05-19 12:20 ` [PATCH v12 1/6] dt-bindings: iio: adc: add AD4691 family Radu Sabau via B4 Relay
2026-05-19 12:28   ` sashiko-bot
2026-05-19 17:26     ` Conor Dooley [this message]
2026-05-19 17:26       ` Conor Dooley
2026-05-22 11:23   ` Jonathan Cameron
2026-05-19 12:20 ` [PATCH v12 2/6] iio: adc: ad4691: add initial driver for " Radu Sabau via B4 Relay
2026-05-22 11:35   ` Jonathan Cameron
2026-05-19 12:20 ` [PATCH v12 3/6] iio: adc: ad4691: add triggered buffer support Radu Sabau via B4 Relay
2026-05-19 13:42   ` sashiko-bot
2026-05-22 11:46   ` Jonathan Cameron
2026-05-19 12:20 ` [PATCH v12 4/6] iio: adc: ad4691: add SPI offload support Radu Sabau via B4 Relay
2026-05-19 14:35   ` sashiko-bot
2026-05-19 12:20 ` [PATCH v12 5/6] iio: adc: ad4691: add oversampling support Radu Sabau via B4 Relay
2026-05-19 15:11   ` sashiko-bot
2026-05-21 11:32   ` Sabau, Radu bogdan
2026-05-22 11:16     ` Jonathan Cameron
2026-05-22 11:38       ` Sabau, Radu bogdan
2026-05-22 13:38         ` Jonathan Cameron
2026-05-19 12:20 ` [PATCH v12 6/6] docs: iio: adc: ad4691: add driver documentation Radu Sabau via B4 Relay
2026-05-22 11:51 ` [PATCH v12 0/6] iio: adc: ad4691: add driver for AD4691 multichannel SAR ADC family Jonathan Cameron

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=20260519-bamboo-gleeful-669dcbefb0a3@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=devnull+radu.sabau.analog.com@kernel.org \
    --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