From: David Lechner <dlechner@baylibre.com>
To: Matti Vaittinen <mazziesaccount@gmail.com>,
Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: ti-adc128s052: Drop variable vref
Date: Mon, 28 Apr 2025 10:16:07 -0500 [thread overview]
Message-ID: <b7adef4b-68ae-4a49-937b-307e116976f4@baylibre.com> (raw)
In-Reply-To: <59106e24332743a7f9eb0b13ad6a2f5595ab485a.1745823530.git.mazziesaccount@gmail.com>
On 4/28/25 2:02 AM, Matti Vaittinen wrote:
> According to Jonathan, variable reference voltages are very rare. It is
> unlikely it is needed, and supporting it makes the code a bit more
> complex.
>
> Simplify the driver and drop the variable vref support.
>
> Suggested-by: Jonathan Cameron <jic23@kernel.org>
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
>
> ---
Reviewed-by: David Lechner <dlechner@baylibre.com>
> @@ -183,17 +173,14 @@ static int adc128_probe(struct spi_device *spi)
> indio_dev->channels = config->channels;
> indio_dev->num_channels = config->num_channels;
>
> - adc->reg = devm_regulator_get(&spi->dev, config->refname);
> - if (IS_ERR(adc->reg))
> - return PTR_ERR(adc->reg);
> -
> - ret = regulator_enable(adc->reg);
> + ret = devm_regulator_get_enable_read_voltage(&spi->dev,
> + config->refname);
Is this properly aligned to the opening "("?
next prev parent reply other threads:[~2025-04-28 15:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 7:02 Matti Vaittinen
2025-04-28 7:08 ` Andy Shevchenko
2025-04-28 9:45 ` Matti Vaittinen
2025-04-28 9:49 ` Andy Shevchenko
2025-04-28 13:10 ` Matti Vaittinen
2025-05-05 16:31 ` Jonathan Cameron
2025-04-28 15:16 ` David Lechner [this message]
2025-04-29 4:10 ` Matti Vaittinen
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=b7adef4b-68ae-4a49-937b-307e116976f4@baylibre.com \
--to=dlechner@baylibre.com \
--cc=andy@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.com \
--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®