From: David Lechner <dlechner@baylibre.com>
To: Ajith Anandhan <ajithanandhan0406@gmail.com>,
Jonathan Cameron <jic23@kernel.org>
Cc: nuno.sa@analog.com, andy@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: adc: Add TI ADS1120 binding
Date: Mon, 15 Dec 2025 09:58:36 -0600 [thread overview]
Message-ID: <8ef3fbd1-b746-4379-b615-e3034ec8f39e@baylibre.com> (raw)
In-Reply-To: <d25b91b2-20c2-492a-b056-bf3bdaf4494a@gmail.com>
On 12/15/25 8:49 AM, Ajith Anandhan wrote:
> On 11/18/25 5:49 AM, David Lechner wrote:
>> On 11/15/25 12:31 PM, Jonathan Cameron wrote:
>>> On Sun, 9 Nov 2025 19:41:18 +0530
>>> Ajith Anandhan <ajithanandhan0406@gmail.com> wrote:
>>>
...
>>>> +
>>>> + ti,avdd-is-ref:
>>>> + type: boolean
>>>> + description: |
>>>> + If present, indicates that the AVDD supply voltage is of sufficient
>>>> + quality and stability to be used as the voltage reference instead of
>>>> + the internal reference. This allows the driver to select AVDD as the
>>>> + reference source for potentially better performance.
>>> This one is interesting as I don't recall anyone arguing this made
>>> sense before. In what way better performance? Are their boards out
>>> there where this definitely makes sense to do?
>>>
>> Seems harmless to have the property even if no one ever uses it. But I would
>> be curious to know the answers to those questions too.
>
>
> I included this property based on the datasheet mentioning AVDD as a possible reference source, butit doesn't claim this provides better performance, and I don't currently have a specific use case or hardware design that requires it.
>
> How to proceed ? Need your valuable suggestions.
>
>
> BR,
>
> Ajith.
>
>>
>
It sounds like it is unlikely to be used in practice, so I won't
object if you want to drop it to keep things simple.
next prev parent reply other threads:[~2025-12-15 15:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-09 14:11 [PATCH v2 0/2] iio: adc: ti-ads1120: Add driver and dt-binding Ajith Anandhan
2025-11-09 14:11 ` [PATCH v2 1/2] dt-bindings: iio: adc: Add TI ADS1120 binding Ajith Anandhan
2025-11-10 7:59 ` Krzysztof Kozlowski
2025-11-15 18:31 ` Jonathan Cameron
2025-11-18 0:19 ` David Lechner
2025-12-15 14:49 ` Ajith Anandhan
2025-12-15 15:58 ` David Lechner [this message]
2025-11-09 14:11 ` [PATCH v2 2/2] iio: adc: Add support for TI ADS1120 Ajith Anandhan
2025-11-09 17:03 ` Andy Shevchenko
2025-11-09 17:05 ` Andy Shevchenko
2025-11-10 10:17 ` kernel test robot
2025-11-15 18:45 ` Jonathan Cameron
2025-11-18 14:04 ` David Lechner
2025-12-15 16:13 ` Ajith Anandhan
2025-12-15 16:36 ` David Lechner
2025-12-15 16:49 ` Ajith Anandhan
2025-12-15 17:00 ` Andy Shevchenko
2025-12-15 17:38 ` Ajith Anandhan
2025-12-15 17:42 ` David Lechner
2025-12-15 17:50 ` Ajith Anandhan
2025-12-21 18:57 ` 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=8ef3fbd1-b746-4379-b615-e3034ec8f39e@baylibre.com \
--to=dlechner@baylibre.com \
--cc=ajithanandhan0406@gmail.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=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