From: "Kurt Borja" <kuurtb@gmail.com>
To: "Conor Dooley" <conor@kernel.org>, "Kurt Borja" <kuurtb@gmail.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 1/3] dt-bindings: iio: adc: Add reference-source property
Date: Fri, 19 Jun 2026 11:30:08 -0500 [thread overview]
Message-ID: <DJD633458PP7.204THMW74YY30@gmail.com> (raw)
In-Reply-To: <20260619-proton-distract-de92d6b9b600@spud>
Hi Conor,
On Fri Jun 19, 2026 at 9:14 AM -05, Conor Dooley wrote:
> On Thu, Jun 18, 2026 at 07:33:01PM -0500, Kurt Borja wrote:
>> Some ADCs have configurable voltage reference sources for each channel.
>>
>> Signed-off-by: Kurt Borja <kuurtb@gmail.com>
>> ---
>> Documentation/devicetree/bindings/iio/adc/adc.yaml | 10 ++++++++++
>> 1 file changed, 10 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/iio/adc/adc.yaml b/Documentation/devicetree/bindings/iio/adc/adc.yaml
>> index b9bc02b5b07a4c..c74c2084fdb68c 100644
>> --- a/Documentation/devicetree/bindings/iio/adc/adc.yaml
>> +++ b/Documentation/devicetree/bindings/iio/adc/adc.yaml
>> @@ -73,6 +73,16 @@ properties:
>> device design and can interact with other characteristics such as
>> settling time.
>>
>> + reference-source:
>> + $ref: /schemas/types.yaml#/definitions/uint32-array
>> + maxItems: 2
>> + minItems: 1
>> + description:
>> + Indicates the voltage reference source or sources for this channel.
>> +
>> + This array describes either a single reference source or a positive and
>> + negative reference sources.
>
> I have no idea from this description what this actually refers to. Is it
> a pin? A supply? A channel?
It can be pins but also can be internal vref sources. Not always a
supply though, in some applications a resistor is connected to the
reference source pins.
If there is a next version I'll clarify it.
>
>> +
>> anyOf:
>> - oneOf:
>> - required:
>>
>> --
>> 2.54.0
>>
--
Thanks,
~ Kurt
next prev parent reply other threads:[~2026-06-19 16:30 UTC|newest]
Thread overview: 16+ 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 14:14 ` Conor Dooley
2026-06-19 16:30 ` Kurt Borja [this message]
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 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=DJD633458PP7.204THMW74YY30@gmail.com \
--to=kuurtb@gmail.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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