From: sashiko-bot@kernel.org
To: "Radu Sabau via B4 Relay" <devnull+radu.sabau.analog.com@kernel.org>
Cc: krzk+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org,
conor+dt@kernel.org
Subject: Re: [PATCH v11 1/6] dt-bindings: iio: adc: add AD4691 family
Date: Fri, 15 May 2026 13:37:52 +0000 [thread overview]
Message-ID: <20260515133752.EE3CCC2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260515-ad4692-multichannel-sar-adc-driver-v11-1-eab27d852ac2@analog.com>
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 the `examples` section.
--
commit 5576d49868d1ae53d794381f2b3e2079954441db
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 defines hardware connections including power
domains, PWM, reset GPIOs, and interrupt sources, along with providing
two binding examples.
> 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
Since the binding defines the device as a GPIO controller, should
gpio-controller and #gpio-cells be added to this required list?
Omitting these properties from the required list might allow incomplete
device tree nodes to pass validation.
[ ... ]
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + /* AD4692 in CNV Burst Mode with SPI offload */
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + adc@0 {
> + compatible = "adi,ad4692";
> + reg = <0>;
> + spi-cpol;
> + spi-cpha;
> + spi-max-frequency = <40000000>;
> +
> + avdd-supply = <&avdd_supply>;
> + ldo-in-supply = <&avdd_supply>;
> + vio-supply = <&vio_supply>;
> + ref-supply = <&ref_5v>;
> +
> + reset-gpios = <&gpio0 15 GPIO_ACTIVE_LOW>;
> +
> + pwms = <&pwm_gen 0 0>;
> +
> + #trigger-source-cells = <1>;
> + };
> + };
Should the gpio-controller and #gpio-cells properties be included in these
examples?
Without them, the examples might fail dt_binding_check if they are added
to the required list above.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260515-ad4692-multichannel-sar-adc-driver-v11-0-eab27d852ac2@analog.com?part=1
next prev parent reply other threads:[~2026-05-15 13:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 13:31 [PATCH v11 0/6] iio: adc: ad4691: add driver for AD4691 multichannel SAR ADC family Radu Sabau via B4 Relay
2026-05-15 13:31 ` Radu Sabau
2026-05-15 13:31 ` [PATCH v11 1/6] dt-bindings: iio: adc: add AD4691 family Radu Sabau via B4 Relay
2026-05-15 13:31 ` Radu Sabau
2026-05-15 13:37 ` sashiko-bot [this message]
2026-05-15 17:08 ` Conor Dooley
2026-05-15 13:31 ` [PATCH v11 2/6] iio: adc: ad4691: add initial driver for " Radu Sabau via B4 Relay
2026-05-15 13:31 ` Radu Sabau
2026-05-15 14:12 ` sashiko-bot
2026-05-15 13:31 ` [PATCH v11 3/6] iio: adc: ad4691: add triggered buffer support Radu Sabau via B4 Relay
2026-05-15 13:31 ` Radu Sabau
2026-05-15 14:55 ` sashiko-bot
2026-05-15 13:31 ` [PATCH v11 4/6] iio: adc: ad4691: add SPI offload support Radu Sabau via B4 Relay
2026-05-15 13:31 ` Radu Sabau
2026-05-15 13:31 ` [PATCH v11 5/6] iio: adc: ad4691: add oversampling support Radu Sabau via B4 Relay
2026-05-15 13:31 ` Radu Sabau
2026-05-15 16:14 ` sashiko-bot
2026-05-15 13:31 ` [PATCH v11 6/6] docs: iio: adc: ad4691: add driver documentation Radu Sabau via B4 Relay
2026-05-15 13:31 ` Radu Sabau
2026-05-15 16:21 ` 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=20260515133752.EE3CCC2BCB0@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+radu.sabau.analog.com@kernel.org \
--cc=krzk+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.