From: sashiko-bot@kernel.org
To: "Stefan Popa" <stefan.popa@analog.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: adc: add maxim,max40080
Date: Wed, 15 Jul 2026 06:45:27 +0000 [thread overview]
Message-ID: <20260715064528.1E3FF1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260715063652.368501-2-stefan.popa@analog.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `shunt-resistor-micro-ohms` property is missing from the `required` list, allowing incomplete hardware descriptions to pass validation.
--
--- Patch [1]: [PATCH v3 1/2] dt-bindings: iio: adc: add maxim,max40080 ---
commit 102dd7d43e2e646eee1b098788f579fc92431947
Author: Stefan Popa <stefan.popa@analog.com>
dt-bindings: iio: adc: add maxim,max40080
This commit adds device tree bindings for the Maxim MAX40080 bidirectional
current-sense amplifier. It defines the required and optional properties for
the device, including an integrated 12-bit ADC and an I2C/SMBus interface.
> diff --git a/Documentation/devicetree/bindings/iio/adc/maxim,max40080.yaml b/Documentation/devicetree/bindings/iio/adc/maxim,max40080.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/adc/maxim,max40080.yaml
[ ... ]
> + shunt-resistor-micro-ohms:
> + description:
> + Value of the current-sense shunt resistor connected between the IN+ and
> + IN- inputs. Used to scale the reported current.
> +
> +required:
> + - compatible
> + - reg
> + - vdd-supply
[Severity: Medium]
Should shunt-resistor-micro-ohms be added to this required list?
Without this property, the schema will silently pass incomplete hardware
descriptions during a dt_binding_check run. A current-sense amplifier
requires a shunt resistor value to correctly scale the measured voltage
drop into a current measurement.
> +
> +additionalProperties: false
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260715063652.368501-1-stefan.popa@analog.com?part=1
next prev parent reply other threads:[~2026-07-15 6:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 6:36 [PATCH v3 0/2] iio: adc: add MAX40080 current-sense amplifier driver Stefan Popa
2026-07-15 6:36 ` [PATCH v3 1/2] dt-bindings: iio: adc: add maxim,max40080 Stefan Popa
2026-07-15 6:45 ` sashiko-bot [this message]
2026-07-15 6:36 ` [PATCH v3 2/2] iio: adc: add MAX40080 current-sense amplifier driver Stefan Popa
2026-07-15 6:46 ` sashiko-bot
2026-07-15 8:34 ` Andy Shevchenko
2026-07-15 6:51 ` [PATCH v3 0/2] " Andy Shevchenko
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=20260715064528.1E3FF1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=stefan.popa@analog.com \
/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