From: David Lechner <dlechner@baylibre.com>
To: Kurt Borja <kuurtb@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: "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 v2 0/3] dt-bindings: iio: adc: Add reference, excitation and burn-out properties
Date: Mon, 22 Jun 2026 15:01:57 -0500 [thread overview]
Message-ID: <f7aae511-0e23-41cf-a5b0-27782caac30b@baylibre.com> (raw)
In-Reply-To: <DJFUE81GZEEG.35TP4FFBVE63B@gmail.com>
On 6/22/26 2:58 PM, Kurt Borja wrote:
> On Mon Jun 22, 2026 at 2:38 PM -05, David Lechner wrote:
>> On 6/22/26 2:30 PM, Kurt Borja wrote:
>>> Hi all,
>>>
>>> After submitting a patch series adding support for TI ADS126X ADCs [1],
>>> I was made aware by David [2] that at least two more chip families,
>>> ads1220 [3] and ads1x2c14, share very similar features (though these
>>> chips are not really compatible between them). After that, I found one
>>> more chip with the same features which is already upstream, the
>>> AD4170-4.
>>>
>>> As David explained in [2], these chips are intended to be used with
>>> RTDs, thermocouples or other resistive sensors so they share the
>>> following per-channel features:
>>>
>>> - Configurable reference selection
>>> - Burn-out Current Sources (BOCS) for diagnostic purpuses
>>> - Excitation current sources (usually called IDACs TI) for sensor
>>> current biasing
>>>
>>> Given that these three features are present in all four devices and
>>> three of these drivers are still under review, my proposal is to have
>>> these features be described in adc.yaml and have this series merged
>>> before the three others [1] [2] [3].
>>>
>>> This series is sent as RFC because I still don't have much experience
>>> with dt-bindings and I don't know if this approach or the properties are
>>> general enough to be described like this.
>>
>> It will probably be easier if I just include these patches when I do
>> v2 of my series (if you don't mind me tweaking them a bit).
>
> Sure, that's fine by me. I'll add a dependency to your series with b4.
>
> Want me to send one more version addressing your comments before you
> take it in?
>
No need. I don't mind fixing it up.
next prev parent reply other threads:[~2026-06-22 20:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 19:30 [PATCH RFC v2 0/3] dt-bindings: iio: adc: Add reference, excitation and burn-out properties Kurt Borja
2026-06-22 19:30 ` [PATCH RFC v2 1/3] dt-bindings: iio: adc: Add reference-source property Kurt Borja
2026-06-22 19:40 ` David Lechner
2026-06-22 19:30 ` [PATCH RFC v2 2/3] dt-bindings: iio: adc: Add excitation current sources properties Kurt Borja
2026-06-22 19:42 ` David Lechner
2026-06-22 19:30 ` [PATCH RFC v2 3/3] dt-bindings: iio: adc: Add burn-out current properties Kurt Borja
2026-06-22 19:44 ` David Lechner
2026-06-22 19:38 ` [PATCH RFC v2 0/3] dt-bindings: iio: adc: Add reference, excitation and burn-out properties David Lechner
2026-06-22 19:58 ` Kurt Borja
2026-06-22 20:01 ` David Lechner [this message]
2026-06-22 20:05 ` 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=f7aae511-0e23-41cf-a5b0-27782caac30b@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuurtb@gmail.com \
--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