From: Joshua Crofts <joshua.crofts1@gmail.com>
To: sashiko-bot@kernel.org
Cc: sashiko-reviews@lists.linux.dev, 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 20:37:16 +0200 [thread overview]
Message-ID: <20260721203716.0fc5313c@systembl0wer> (raw)
In-Reply-To: <20260721183358.67E151F00A3D@smtp.kernel.org>
On Tue, 21 Jul 2026 18:33:58 +0000
sashiko-bot@kernel.org wrote:
Clarifying Sashiko's comment:
> [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.
Yes, the MCP47A1 does have a physical VREF pin, as seen in the block diagram:
https://ww1.microchip.com/downloads/aemDocuments/documents/OTH/ProductDocuments/DataSheets/25154A.pdf
--
Kind regards,
Joshua Crofts
next prev parent reply other threads:[~2026-07-21 18:37 UTC|newest]
Thread overview: 17+ 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
2026-07-21 18:37 ` Joshua Crofts [this message]
2026-07-22 16:47 ` Conor Dooley
2026-07-24 23:04 ` Jonathan Cameron
2026-07-24 23:04 ` Jonathan Cameron
2026-07-25 8:12 ` Joshua Crofts
2026-07-25 15:41 ` David Lechner
2026-07-25 21:54 ` Jonathan Cameron
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
2026-07-22 6:30 ` Joshua Crofts
2026-07-25 16:52 ` David Lechner
2026-07-24 23:14 ` Jonathan Cameron
2026-07-25 10:17 ` Joshua Crofts
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=20260721203716.0fc5313c@systembl0wer \
--to=joshua.crofts1@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-bot@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