From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Lechner <dlechner@baylibre.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Linus Walleij" <linusw@kernel.org>,
"Bartosz Golaszewski" <brgl@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-gpio@vger.kernel.org,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>
Subject: Re: [PATCH v3 5/6] iio: adc: ti-ads7950: switch to using devm_regulator_get_enable_read_voltage()
Date: Sat, 7 Mar 2026 18:04:33 +0000 [thread overview]
Message-ID: <aaxoIWL7NIa-2VkU@google.com> (raw)
In-Reply-To: <27ffa24d-a388-46eb-8df7-04624cd32ea1@baylibre.com>
On Sat, Mar 07, 2026 at 11:43:32AM -0600, David Lechner wrote:
> On 3/7/26 5:49 AM, Jonathan Cameron wrote:
> > On Thu, 05 Mar 2026 11:21:56 -0800
> > Dmitry Torokhov <dmitry.torokhov@gmail.com> wrote:
> >
> >> The regulator is enabled for the entire time the driver is bound to the
> >> device, and we only need to access it to fetch voltage, which can be
> >> done at probe time.
> >>
> >> Switch to using devm_regulator_get_enable_read_voltage() which
> >> simplifies probing and unbinding code.
> >>
> >> Suggested-by: David Lechner <dlechner@baylibre.com>
> >> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > Hi.
> >
> > I think this broke the ACPI case (where regulator isn't available).
Oh, you're right.
> >
> > Jonathan
> >
> >> ---
> >> drivers/iio/adc/ti-ads7950.c | 45 +++++++++++---------------------------------
> >> 1 file changed, 11 insertions(+), 34 deletions(-)
> >>
> >> diff --git a/drivers/iio/adc/ti-ads7950.c b/drivers/iio/adc/ti-ads7950.c
> >> index 273c35e03185..847e83baa876 100644
> >> --- a/drivers/iio/adc/ti-ads7950.c
> >> +++ b/drivers/iio/adc/ti-ads7950.c
> >> @@ -341,19 +341,9 @@ static int ti_ads7950_scan_direct(struct iio_dev *indio_dev, unsigned int ch)
> >> return st->single_rx;
> >> }
> >>
> >> -static int ti_ads7950_get_range(struct ti_ads7950_state *st)
> >> +static unsigned int ti_ads7950_get_range(struct ti_ads7950_state *st)
> >> {
> >> - int vref;
> >> -
> >> - if (st->vref_mv) {
> >> - vref = st->vref_mv;
> >> - } else {
> >> - vref = regulator_get_voltage(st->reg);
> >> - if (vref < 0)
> >> - return vref;
> >> -
> >> - vref /= 1000;
> >> - }
> >> + unsigned int vref = st->vref_mv;
> >>
> >> if (st->cmd_settings_bitmask & TI_ADS7950_CR_RANGE_5V)
> >> vref *= 2;
> >> @@ -382,11 +372,7 @@ static int ti_ads7950_read_raw(struct iio_dev *indio_dev,
> >>
> >> return IIO_VAL_INT;
> >> case IIO_CHAN_INFO_SCALE:
> >> - ret = ti_ads7950_get_range(st);
> >> - if (ret < 0)
> >> - return ret;
> >> -
> >> - *val = ret;
> >> + *val = ti_ads7950_get_range(st);
> >> *val2 = (1 << chan->scan_type.realbits) - 1;
> >>
> >> return IIO_VAL_FRACTIONAL;
> >> @@ -580,30 +566,24 @@ static int ti_ads7950_probe(struct spi_device *spi)
> >> spi_message_init_with_transfers(&st->scan_single_msg,
> >> st->scan_single_xfer, 3);
> >>
> >> + ret = devm_regulator_get_enable_read_voltage(&spi->dev, "vref");
> >> + if (ret < 0)
> >
> > I think you need to check for -ENODEV and if you see than then
> > see if the acpi route below applies. Otherwise on ACPI this will fail
> > and we'll fail the probe.
> >
>
> Or do something like:
>
> if (ACPI_COMPANION(&spi->dev)) {
> ret = devm_regulator_get_enable(&spi->dev, "vref");
> if (ret)
> return dev_err_probe(&spi->dev, ret,
> "Failed to get regulator \"vref\"\n");
>
> st->vref_mv = TI_ADS7950_VA_MV_ACPI_DEFAULT;
We know that concept of regulators is not exposed on ACPI systems, and
we'd get a dummy here, so maybe just store st->vref_mv and not bother
with acquiring and enabling the dummy regulator?
Thanks.
--
Dmitry
next prev parent reply other threads:[~2026-03-07 18:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 19:21 [PATCH v3 0/6] ti-ads7950: fix gpio handling and facelift Dmitry Torokhov
2026-03-05 19:21 ` [PATCH v3 1/6] iio: adc: ti-ads7950: normalize return value of gpio_get Dmitry Torokhov
2026-03-05 19:21 ` [PATCH v3 2/6] iio: adc: ti-ads7950: do not clobber gpio state in ti_ads7950_get() Dmitry Torokhov
2026-03-05 19:21 ` [PATCH v3 3/6] iio: adc: ti-ads7950: switch to using guard() notation Dmitry Torokhov
2026-03-07 17:34 ` David Lechner
2026-03-05 19:21 ` [PATCH v3 4/6] iio: adc: ti-ads7950: simplify check for spi_setup() failures Dmitry Torokhov
2026-03-07 11:46 ` Jonathan Cameron
2026-03-07 17:35 ` David Lechner
2026-03-05 19:21 ` [PATCH v3 5/6] iio: adc: ti-ads7950: switch to using devm_regulator_get_enable_read_voltage() Dmitry Torokhov
2026-03-07 11:49 ` Jonathan Cameron
2026-03-07 17:43 ` David Lechner
2026-03-07 18:04 ` Dmitry Torokhov [this message]
2026-03-07 18:07 ` David Lechner
2026-03-08 18:29 ` Jonathan Cameron
2026-03-08 20:32 ` Andy Shevchenko
2026-03-09 5:35 ` Dmitry Torokhov
2026-03-09 8:52 ` Andy Shevchenko
2026-03-05 19:21 ` [PATCH v3 6/6] iio: adc: ti-ads7950: complete conversion to using managed resources Dmitry Torokhov
2026-03-06 12:21 ` Andy Shevchenko
2026-03-07 18:05 ` Dmitry Torokhov
2026-03-07 17:50 ` David Lechner
2026-03-07 21:47 ` David Lechner
2026-03-07 11:42 ` [PATCH v3 0/6] ti-ads7950: fix gpio handling and facelift 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=aaxoIWL7NIa-2VkU@google.com \
--to=dmitry.torokhov@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy@kernel.org \
--cc=brgl@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--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