From: Jonathan Cameron <jic23@kernel.org>
To: David Lechner <dlechner@baylibre.com>
Cc: "Cong Nguyen" <congnt264@gmail.com>,
"Matteo Martelli" <matteomartelli3@gmail.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Ariana Lazar" <ariana.lazar@microchip.com>
Subject: Re: [PATCH] iio: adc: pac1921: fix wrong channel used in trigger handler read
Date: Sun, 2 Aug 2026 19:25:51 +0100 [thread overview]
Message-ID: <20260802192551.76ab4a2b@jic23-huawei> (raw)
In-Reply-To: <06f059d0-ac5f-408e-81ed-220f4cb1daf5@baylibre.com>
On Sun, 2 Aug 2026 10:48:26 -0500
David Lechner <dlechner@baylibre.com> wrote:
> On 8/2/26 2:12 AM, Cong Nguyen wrote:
> > pac1921_trigger_handler() walks the enabled channels with
> > iio_for_each_active_channel(), which yields the scan index (bit) of each
> > active channel, while ch is a separate counter used to pack the samples
> > contiguously into the scan buffer.
> >
> > The register to read was looked up with the packing counter instead of
> > the scan index:
> >
> > ret = pac1921_read_res(priv, idev->channels[ch].address, &val);
> >
> > pac1921_channels[] is ordered by scan index, so channels[bit] is the
> > channel that is actually enabled, whereas channels[ch] is merely the
> > ch-th array entry. These coincide only when the enabled channels form a
> > contiguous prefix (e.g. all channels enabled). With a sparse scan mask -
> > for example when only the power channel (scan index 3) is enabled - the
> > handler reads the wrong register (VBUS instead of VPOWER) and pushes it
> > to userspace as the enabled channel's data.
> >
> > Index the channel array by the scan index (bit) to read the correct
> > register, keeping ch only for contiguous packing into the scan buffer.
> >
> > Fixes: 371f778b83cd ("iio: adc: add support for pac1921")
> > Cc: stable@vger.kernel.org
> > Assisted-by: Claude:claude-opus-4
> > Signed-off-by: Cong Nguyen <congnt264@gmail.com>
> > ---
> > drivers/iio/adc/pac1921.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/adc/pac1921.c b/drivers/iio/adc/pac1921.c
> > index bce7185953ec..0037509503ed 100644
> > --- a/drivers/iio/adc/pac1921.c
> > +++ b/drivers/iio/adc/pac1921.c
> > @@ -1037,7 +1037,7 @@ static irqreturn_t pac1921_trigger_handler(int irq, void *p)
> > iio_for_each_active_channel(idev, bit) {
> > u16 val;
> >
> > - ret = pac1921_read_res(priv, idev->channels[ch].address, &val);
> > + ret = pac1921_read_res(priv, idev->channels[bit].address, &val);
> > if (ret)
> > goto done;
> >
>
> Looks correct.
>
> Reviewed-by: David Lechner <dlechner@baylibre.com>
+CC Ariana who is dealing with similar parts and might be able to sanity
check this.
FWIW looks correct to me too.
Jonathan
>
next prev parent reply other threads:[~2026-08-02 18:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-02 7:12 [PATCH] iio: adc: pac1921: fix wrong channel used in trigger handler read Cong Nguyen
2026-08-02 15:48 ` David Lechner
2026-08-02 18:25 ` Jonathan Cameron [this message]
2026-08-04 6:49 ` Matteo Martelli
2026-08-04 23:34 ` 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=20260802192551.76ab4a2b@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=ariana.lazar@microchip.com \
--cc=congnt264@gmail.com \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matteomartelli3@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.