Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Joshua Crofts" <joshua.crofts1@gmail.com>
Cc: robh@kernel.org, devicetree@vger.kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: dac: add support for mcp47a1
Date: Tue, 21 Jul 2026 18:33:58 +0000	[thread overview]
Message-ID: <20260721183358.67E151F00A3D@smtp.kernel.org> (raw)
In-Reply-To: <20260721-mcp47a1-add-support-v1-1-da045a2567e3@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The binding incorrectly requires `vref-supply`, but the MCP47A1 likely does not have a dedicated VREF pin.
--

--- Patch [1]: [PATCH 1/2] dt-bindings: iio: dac: add support for mcp47a1 ---
commit d1dc3c2e573f4f52e69aabeb608ccb23acd5a123
Author: Joshua Crofts <joshua.crofts1@gmail.com>

dt-bindings: iio: dac: add support for mcp47a1

This commit introduces the device tree bindings and MAINTAINERS entry for
the Microchip MCP47A1, a 6-bit volatile digital-to-analog converter.

> diff --git a/Documentation/devicetree/bindings/iio/dac/microchip,mcp47a1.yaml b/Documentation/devicetree/bindings/iio/dac/microchip,mcp47a1.yaml
> new file mode 100644
> index 0000000000000..3322fca03b3a7
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/dac/microchip,mcp47a1.yaml
[ ... ]
> +required:
> +  - compatible
> +  - reg
> +  - vref-supply

[Severity: Medium]
Does the MCP47A1 actually have a dedicated VREF pin? Standard Microchip I2C
DACs in this class (such as the 6-pin MCP4725) typically use VDD as their
voltage reference.

If there is no physical VREF pin on this hardware, requiring vref-supply
here forces device tree authors to define dummy regulators in their
device trees just to pass schema validation.

> +  - vdd-supply
> +
> +additionalProperties: false

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260721-mcp47a1-add-support-v1-0-da045a2567e3@gmail.com?part=1

  reply	other threads:[~2026-07-21 18:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 18:24 [PATCH 0/2] iio: dac: mcp47a1: add support for new device Joshua Crofts
2026-07-21 18:24 ` [PATCH 1/2] dt-bindings: iio: dac: add support for mcp47a1 Joshua Crofts
2026-07-21 18:33   ` sashiko-bot [this message]
2026-07-21 18:37     ` Joshua Crofts
2026-07-21 18:24 ` [PATCH 2/2] iio: dac: mcp47a1: add support for new device Joshua Crofts
2026-07-21 19:20   ` sashiko-bot
2026-07-21 20:47   ` 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=20260721183358.67E151F00A3D@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=joshua.crofts1@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox