From: David Lechner <dlechner@baylibre.com>
To: Andy Shevchenko <andriy.shevchenko@intel.com>,
Ariana Lazar <ariana.lazar@microchip.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Dan Carpenter" <error27@gmail.com>
Subject: Re: [PATCH] iio: dac: Fix passing uninitialized vref1_uV for no Vref1 case
Date: Tue, 14 Apr 2026 08:21:00 -0500 [thread overview]
Message-ID: <70eb71c1-d239-4618-a12b-e64fff8e54d2@baylibre.com> (raw)
In-Reply-To: <ad43ofFZwzEkYifY@ashevche-desk.local>
On 4/14/26 7:48 AM, Andy Shevchenko wrote:
> On Tue, Apr 14, 2026 at 03:33:38PM +0300, Ariana Lazar wrote:
>> Initialize vref1_uV variable to 0 before calling
>> mcp47feb02_init_ch_scales() in mcp47feb02_probe() to avoid passing an
>> uninitialized value when have_ext_vref1 is false.
>
> ...
>
>> + vref1_uV = 0;
>> if (chip_features->have_ext_vref1) {
>
> I'm wondering what will happen if we do the below unconditionally?
>
>> ret = devm_regulator_get_enable_read_voltage(dev, "vref1");
>
> If we have no regulator, we get a dummy one, right? What is the voltage will
> be? 0?
It will fail with -EINVAL because dummy regulator doesn't have a
voltage specified anywhere.
>
>> if (ret > 0) {
>> vref1_uV = ret;
>> data->use_vref1 = true;
>> } else {
>> - vref1_uV = 0;
>> dev_dbg(dev, "using internal band gap as voltage reference 1.\n");
>> dev_dbg(dev, "Vref1 is unavailable.\n");
>> }
>
next prev parent reply other threads:[~2026-04-14 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 12:33 [PATCH] iio: dac: Fix passing uninitialized vref1_uV for no Vref1 case Ariana Lazar
2026-04-14 12:48 ` Andy Shevchenko
2026-04-14 13:21 ` David Lechner [this message]
2026-04-14 16:18 ` Andy Shevchenko
2026-04-14 16:19 ` Andy Shevchenko
2026-04-14 14:26 ` Ariana.Lazar
2026-04-14 16:26 ` Andy Shevchenko
2026-04-20 12:19 ` Jonathan Cameron
2026-04-14 15:32 ` David Lechner
2026-04-14 16:28 ` Andy Shevchenko
2026-04-20 12:11 ` 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=70eb71c1-d239-4618-a12b-e64fff8e54d2@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=ariana.lazar@microchip.com \
--cc=error27@gmail.com \
--cc=jic23@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