From: sashiko-bot@kernel.org
To: "Kurt Borja" <kuurtb@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH RFC 3/3] dt-bindings: iio: adc: Add burn-out current properties
Date: Fri, 19 Jun 2026 00:45:32 +0000 [thread overview]
Message-ID: <20260619004533.203551F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260618-new-channel-props-v1-3-963c1b5cf40a@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The `burn-out-current-microamp` property lacks array bounds (e.g., `maxItems`), allowing unbounded arrays to silently pass schema validation.
- [Low] The description for `burn-out-current-polarity` is incorrectly copy-pasted from `burn-out-current-microamp` and fails to describe the polarity property itself.
--
commit a77887c22cdfb0d199c09b61e65157768374c14a
Author: Kurt Borja <kuurtb@gmail.com>
dt-bindings: iio: adc: Add burn-out current properties
This commit adds the burn-out-current-microamp and burn-out-current-polarity
properties to the generic IIO ADC bindings to allow configuration of burn-out
current sources.
> diff --git a/Documentation/devicetree/bindings/iio/adc/adc.yaml b/Documentation/devicetree/bindings/iio/adc/adc.yaml
> --- a/Documentation/devicetree/bindings/iio/adc/adc.yaml
> +++ b/Documentation/devicetree/bindings/iio/adc/adc.yaml
> @@ -106,6 +106,20 @@ properties:
> This array describes the current configuration of the excitation current
> sources or the single matched current for all sources.
>
> + burn-out-current-microamp:
> + description:
> + Burn-out current sources provide current to the channel's input pins for
> + open-circuit or short-circuit detection.
[Severity: Medium]
Since standard device tree schema tools automatically map properties ending in
"-microamp" to an array structure, does this property need an array bound like
maxItems? Without bounds, the schema validator might incorrectly accept an
array of arbitrary size instead of enforcing a single configuration value per
channel.
> +
> + burn-out-current-polarity:
> + $ref: /schemas/types.yaml#/definitions/string
> + description:
> + Burn-out current sources provide current to the channel's input pins for
> + open-circuit or short-circuit detection.
[Severity: Low]
This isn't a bug, but it looks like this description was copy-pasted from
burn-out-current-microamp. Could the description be updated to explain what
the polarity configuration (pull-up/pull-down) actually does?
> + enum:
> + - pull-up
> + - pull-down
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260618-new-channel-props-v1-0-963c1b5cf40a@gmail.com?part=3
next prev parent reply other threads:[~2026-06-19 0:45 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-19 0:33 [PATCH RFC 0/3] dt-bindings: iio: adc: Add reference, excitation and burn-out properties Kurt Borja
2026-06-19 0:33 ` [PATCH RFC 1/3] dt-bindings: iio: adc: Add reference-source property Kurt Borja
2026-06-19 0:40 ` sashiko-bot
2026-06-19 14:14 ` Conor Dooley
2026-06-19 16:30 ` Kurt Borja
2026-06-19 14:24 ` David Lechner
2026-06-19 16:42 ` Kurt Borja
2026-06-19 0:33 ` [PATCH RFC 2/3] dt-bindings: iio: adc: Add excitation current sources properties Kurt Borja
2026-06-19 14:27 ` David Lechner
2026-06-19 16:44 ` Kurt Borja
2026-06-20 15:55 ` David Lechner
2026-06-19 0:33 ` [PATCH RFC 3/3] dt-bindings: iio: adc: Add burn-out current properties Kurt Borja
2026-06-19 0:45 ` sashiko-bot [this message]
2026-06-19 14:28 ` David Lechner
2026-06-19 16:46 ` Kurt Borja
2026-06-20 15:57 ` David Lechner
2026-06-19 14:23 ` [PATCH RFC 0/3] dt-bindings: iio: adc: Add reference, excitation and burn-out properties David Lechner
2026-06-19 16:35 ` Kurt Borja
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=20260619004533.203551F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kuurtb@gmail.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 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.