From: sashiko-bot@kernel.org
To: "Antoniu Miclaus" <antoniu.miclaus@analog.com>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: adc: ad4080: add AD4885 support
Date: Mon, 07 Sep 2026 10:28:26 +0000 [thread overview]
Message-ID: <20260907102827.02AA31F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260907101944.9748-2-antoniu.miclaus@analog.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The schema fails to enforce the presence of the `io-backends` property, despite the commit message explicitly stating it is required.
--
commit 9fc058b2c408d54ffde599d33ff5e645acdf0ad1
Author: Antoniu Miclaus <antoniu.miclaus@analog.com>
dt-bindings: iio: adc: ad4080: add AD4885 support
Add AD4885 compatible string to the AD4080 devicetree binding. The AD4885
is a dual-channel variant that requires two SPI chip selects and two
io-backends for its independent ADC channels.
> diff --git a/Documentation/devicetree/bindings/iio/adc/adi,ad4080.yaml b/Documentation/devicetree/bindings/iio/adc/adi,ad4080.yaml
> index db8467b98e67d..07ac4e07f415a 100644
> --- a/Documentation/devicetree/bindings/iio/adc/adi,ad4080.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/adi,ad4080.yaml
[ ... ]
> @@ -105,6 +106,7 @@ allOf:
> - adi,ad4880
> - adi,ad4883
> - adi,ad4884
> + - adi,ad4885
> then:
> properties:
> reg:
[Severity: Medium]
The commit message states that the AD4885 "requires two SPI chip selects and
two io-backends for its independent ADC channels."
While this conditional block applies constraints to the newly added adi,ad4885
variant, it does not enforce the presence of the io-backends property:
then:
properties:
reg:
minItems: 2
io-backends:
minItems: 2
Should a required directive be added to this block to enforce the presence of
the io-backends property as claimed in the commit message?
then:
properties:
...
required:
- io-backends
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260907101944.9748-1-antoniu.miclaus@analog.com?part=1
next prev parent reply other threads:[~2026-09-07 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 10:19 [PATCH 0/2] iio: adc: ad4080: add support for AD4885 Antoniu Miclaus
2026-09-07 10:19 ` [PATCH 1/2] dt-bindings: iio: adc: ad4080: add AD4885 support Antoniu Miclaus
2026-09-07 10:28 ` sashiko-bot [this message]
2026-09-07 10:19 ` [PATCH 2/2] iio: adc: ad4080: add support for AD4885 Antoniu Miclaus
2026-09-13 22:21 ` 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=20260907102827.02AA31F00A3A@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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.