From: sashiko-bot@kernel.org
To: "Janani Sunil" <janani.sunil@analog.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH 1/6] dt-bindings: iio: adc: Add AD7768
Date: Thu, 09 Jul 2026 08:59:34 +0000 [thread overview]
Message-ID: <20260709085934.D02931F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260709-ad7768-driver-v1-1-44e1194fd96a@analog.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Hardware Variant Required Properties Violation: Missing GPIO provider properties in the required list
--
--- Patch [1]: [PATCH 1/6] dt-bindings: iio: adc: Add AD7768 ---
commit b348e8650b6dd32f354ad1a32b48736f30d333db
Author: Janani Sunil <janani.sunil@analog.com>
dt-bindings: iio: adc: Add AD7768
Devicetree Bindings for AD7768-4 (4 channel) and AD7768 (8 channel)
simultaneous sampling ADC
> diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad7768.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad7768.yaml
> new file mode 100644
> index 0000000000000..b74fe6aef01c6
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad7768.yaml
[ ... ]
> +required:
> + - compatible
> + - reg
> + - clocks
> + - avdd-supply
> + - avss-supply
> + - dvdd-supply
> + - iovdd-supply
> + - vref-supply
> + - adi,data-lines-number
> + - adi,common-mode-output
> + - io-backends
[Severity: Medium]
Since this hardware provides GPIO capabilities, should gpio-controller and
#gpio-cells be included in this required list? Omitting these allows
incomplete device tree nodes to silently pass schema validation.
[ ... ]
> + - |
> + spi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + adc@1 {
> + compatible = "adi,ad7768-4";
> + reg = <1>;
> + spi-max-frequency = <1000000>;
> +
> + avdd-supply = <&avdd_regulator>;
> + avss-supply = <&avss_regulator>;
> + dvdd-supply = <&dvdd_regulator>;
> + iovdd-supply = <&iovdd_regulator>;
> + vref-supply = <&vref_regulator>;
> +
> + clocks = <&ad7768_mclk>;
> +
> + adi,data-lines-number = <4>;
> + adi,common-mode-output = "2.14V";
> + adi,power-mode = "fast";
> +
> + io-backends = <&iio_backend>;
[Severity: Medium]
If the GPIO properties are added to the required list, they will also need
to be included in this example block to pass dt_binding_check validation.
Could gpio-controller and #gpio-cells = <2>; be added here?
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260709-ad7768-driver-v1-0-44e1194fd96a@analog.com?part=1
next prev parent reply other threads:[~2026-07-09 8:59 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 8:50 [PATCH 0/6] iio: adc: Add AD7768/AD7768-4 ADC driver support Janani Sunil
2026-07-09 8:50 ` [PATCH 1/6] dt-bindings: iio: adc: Add AD7768 Janani Sunil
2026-07-09 8:59 ` sashiko-bot [this message]
2026-07-09 15:43 ` David Lechner
2026-07-10 0:33 ` Jonathan Cameron
2026-07-11 14:40 ` David Lechner
2026-07-10 1:39 ` Jonathan Cameron
2026-07-09 8:50 ` [PATCH 2/6] iio: backend: Add support for CRC Janani Sunil
2026-07-09 9:03 ` sashiko-bot
2026-07-10 0:36 ` Jonathan Cameron
2026-07-09 8:50 ` [PATCH 3/6] iio: adc: adi-axi-adc: " Janani Sunil
2026-07-09 9:14 ` sashiko-bot
2026-07-09 15:54 ` David Lechner
2026-07-10 0:39 ` Jonathan Cameron
2026-07-10 0:46 ` Jonathan Cameron
2026-07-09 8:50 ` [PATCH 4/6] iio: adc: Add AD7768 IIO Driver support Janani Sunil
2026-07-09 9:27 ` sashiko-bot
2026-07-10 2:10 ` Jonathan Cameron
2026-07-10 7:41 ` Uwe Kleine-König
2026-07-09 8:50 ` [PATCH 5/6] gpio: ad7768: Add AD7768 GPIO auxiliary driver Janani Sunil
2026-07-09 9:38 ` sashiko-bot
2026-07-09 11:05 ` Andy Shevchenko
2026-07-10 2:14 ` Jonathan Cameron
2026-07-10 20:06 ` Linus Walleij
2026-07-09 8:50 ` [PATCH 6/6] Documentation: iio: Add AD7768 Documentation Janani Sunil
2026-07-09 9:41 ` sashiko-bot
2026-07-10 2:16 ` 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=20260709085934.D02931F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=janani.sunil@analog.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