From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Ariana Lazar" <ariana.lazar@microchip.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: iio: dac: adding support for Microchip MCP47FEB02
Date: Sat, 27 Sep 2025 18:00:56 +0100 [thread overview]
Message-ID: <20250927180056.38b1822f@jic23-huawei> (raw)
In-Reply-To: <7836f862-5320-4a81-b15b-4ada08e78077@baylibre.com>
> > + vref-supply:
> > + description: |
> > + Vref pin is used as a voltage reference when this supply is specified.
> > + Into the datasheet it could be found as a Vref0.
> > + If it does not exists the internal reference will be used.
>
> It looks like there is also the possibility to use V_DD as the reference
> voltage. Not sure the best way to handle that though.
Indeed that's awkward. I suppose a custom property as choice of VDD or internal
reference is unusual and it might be critical to how what is downstream of the DAC
so we can't even do it via userspace _scale control.
I'm lazy so haven't checked the values. If the internal reference is near VDD
it is probably safe enough to just make this a userspace problem if anyone
ever needs it.
next prev parent reply other threads:[~2025-09-27 17:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 11:30 [PATCH 0/2] Adding support for Microchip MCP47FEB02 Ariana Lazar
2025-09-22 11:30 ` [PATCH 1/2] dt-bindings: iio: dac: adding " Ariana Lazar
2025-09-22 16:38 ` Rob Herring (Arm)
2025-09-22 21:59 ` David Lechner
2025-09-27 17:00 ` Jonathan Cameron [this message]
2025-09-22 22:00 ` Rob Herring
2025-09-22 11:30 ` [PATCH 2/2] " Ariana Lazar
2025-09-22 20:10 ` Nuno Sá
2025-09-22 22:15 ` David Lechner
2025-09-23 8:21 ` Nuno Sá
2025-09-27 17:13 ` Jonathan Cameron
2025-09-29 5:44 ` Nuno Sá
2025-09-26 15:38 ` Dan Carpenter
2025-09-27 17:53 ` 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=20250927180056.38b1822f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=ariana.lazar@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
/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