From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Fabrice Gasnier <fabrice.gasnier@foss.st.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Olivier Moysan" <olivier.moysan@foss.st.com>,
linux-iio@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Sashiko <sashiko-bot@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] iio: adc: stm32-adc: fix check on internal channel availability
Date: Wed, 16 Sep 2026 10:45:14 +0300 [thread overview]
Message-ID: <aqpJCsBNKDSKlfFD@ashevche-desk.local> (raw)
In-Reply-To: <20260915-adc-fix-intchan-v1-v1-1-761a1b35001b@foss.st.com>
On Tue, Sep 15, 2026 at 06:15:49PM +0200, Fabrice Gasnier wrote:
> If an unsupported internal channel like vddgpu is requested, the driver
> prints a warning but falls through and assigns it a valid int_ch below.
>
> This causes a problem later during setup:
> stm32_adc_int_ch_enable() {
> ...
> case STM32_ADC_INT_CH_VDDGPU:
> stm32_adc_set_bits(adc, adc->cfg->regs->or_vddgpu.reg,
> adc->cfg->regs->or_vddgpu.mask);
> ...
> }
>
> Because the register offset is uninitialized (0), this performs a
> read-modify-write on offset 0, which corresponds to the ISR register.
>
> Fix this by returning before a valid int_ch is assigned.
> Choice is made to just warn about the channel name as it could
> be confusing, rather than making the probe fail.
Are this and the other patch made with AI assistance?
...
> struct stm32_adc *adc = iio_priv(indio_dev);
> u16 vrefint;
> - int i, ret;
> + int i, ret = 0;
No, either assign closer to its first user, or do even better.
> for (i = 0; i < STM32_ADC_INT_CH_NB; i++) {
> if (!strncmp(stm32_adc_ic[i].name, ch_name, STM32_ADC_CH_SZ)) {
> @@ -2267,31 +2267,36 @@ static int stm32_adc_populate_int_ch(struct iio_dev *indio_dev, const char *ch_n
> switch (i) {
> case STM32_ADC_INT_CH_VDDCORE:
> if (!adc->cfg->regs->or_vddcore.reg)
> - dev_warn(&indio_dev->dev,
> - "%s channel not available\n", ch_name);
> + ret = -ENOENT;
This is a repetition of the same value. Instead add a boolean flag and do here
bool na;
...
na = false; // or can be dropped with 'default' case
switch (i) {
case STM32_ADC_INT_CH_VDDCORE:
na = !adc->cfg->regs->or_vddcore.reg;
> break;
> case STM32_ADC_INT_CH_VDDCPU:
> if (!adc->cfg->regs->or_vddcpu.reg)
> - dev_warn(&indio_dev->dev,
> - "%s channel not available\n", ch_name);
> + ret = -ENOENT;
> break;
> case STM32_ADC_INT_CH_VDDQ_DDR:
> if (!adc->cfg->regs->or_vddq_ddr.reg)
> - dev_warn(&indio_dev->dev,
> - "%s channel not available\n", ch_name);
> + ret = -ENOENT;
> break;
> case STM32_ADC_INT_CH_VREFINT:
> if (!adc->cfg->regs->ccr_vref.reg)
> - dev_warn(&indio_dev->dev,
> - "%s channel not available\n", ch_name);
> + ret = -ENOENT;
> break;
> case STM32_ADC_INT_CH_VBAT:
> if (!adc->cfg->regs->ccr_vbat.reg)
> - dev_warn(&indio_dev->dev,
> - "%s channel not available\n", ch_name);
> + ret = -ENOENT;
> break;
Don't you also need a default?
default:
return -EINVAL; // for example...
> }
if (na) {
...
return 0;
}
>
> + if (ret) {
> + /*
> + * Confusing channel label matches an internal STM32 ADC channel.
> + * Just warn about it, as there's normally no restriction on the
> + * name but that's not among supported internal channels.
> + */
> + dev_warn(&indio_dev->dev, "no %s internal channel\n", ch_name);
> + return 0;
My gosh, the ret value is even ignored!
> + }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-09-16 7:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 16:15 Fabrice Gasnier
2026-09-16 7:45 ` Andy Shevchenko [this message]
2026-09-16 10:02 ` Fabrice Gasnier
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=aqpJCsBNKDSKlfFD@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=alexandre.torgue@foss.st.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=fabrice.gasnier@foss.st.com \
--cc=jic23@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=nuno.sa@analog.com \
--cc=olivier.moysan@foss.st.com \
--cc=sashiko-bot@kernel.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®