From: Stefano Manni <stefano.manni@gmail.com>
To: lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Stefano Manni <stefano.manni@gmail.com>
Subject: [PATCH v2 0/2] iio: adc: ad799x: reference voltage capability
Date: Thu, 7 Aug 2025 09:48:48 +0200 [thread overview]
Message-ID: <20250807074850.130831-1-stefano.manni@gmail.com> (raw)
This patch series refactors 6b104e7895ab16b9b7f466c5f2ca282b87f661e8
in order to add the capability of the chip to have an
external reference voltage into the chip_info struct.
And so avoid ugly conditional checks on the chip id.
In addition the AD7994 is marked to have the external
reference voltage as well.
Changes in v2 compared to v1 [1]:
* remove has_vref from the chips that do not support it,
rely on the default false value
* remove useless message "Supplied reference not supported"
shown for all the chips with has_vref = false
* refactor check on regulator being err or zero
* add external reference to ad7994 as oneliner
[1] https://lore.kernel.org/linux-iio/20250806090158.117628-1-stefano.manni@gmail.com/
Stefano Manni (2):
iio: adc: ad799x: add reference voltage capability to chip_info
iio: adc: ad799x: add reference voltage to ad7994
drivers/iio/adc/ad799x.c | 30 +++++++++++++-----------------
1 file changed, 13 insertions(+), 17 deletions(-)
--
2.48.1
next reply other threads:[~2025-08-07 7:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 7:48 Stefano Manni [this message]
2025-08-07 7:48 ` [PATCH v2 1/2] iio: adc: ad799x: add reference voltage capability to chip_info Stefano Manni
2025-08-07 21:05 ` Andy Shevchenko
2025-08-07 7:48 ` [PATCH v2 2/2] iio: adc: ad799x: add reference voltage to ad7994 Stefano Manni
2025-08-07 21:06 ` Andy Shevchenko
2025-08-07 15:47 ` [PATCH v2 0/2] iio: adc: ad799x: reference voltage capability David Lechner
2025-08-09 19:33 ` 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=20250807074850.130831-1-stefano.manni@gmail.com \
--to=stefano.manni@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
/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
all inboxes | Powered by JetHome®