From: Lukas Schmid <lukas.schmid@netcube.li>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: RESEND [PATCH v1] iio: potentiometer: mcp4131: fix double application of wiper shift
Date: Mon, 02 Feb 2026 21:59:20 +0100 [thread overview]
Message-ID: <4588657.ElGaqSPkdT@lukas-hpz440workstation> (raw)
In-Reply-To: <20260202203443.607eb65a@jic23-huawei>
[-- Attachment #1: Type: text/plain, Size: 2651 bytes --]
On Montag, 2. Februar 2026 21:34:43 Mitteleuropäische Normalzeit Jonathan
Cameron wrote:
> On Mon, 2 Feb 2026 20:29:20 +0000
>
> Jonathan Cameron <jic23@kernel.org> wrote:
> > On Mon, 2 Feb 2026 21:15:35 +0100
> >
> > Lukas Schmid <lukas.schmid@netcube.li> wrote:
> > > The MCP4131 wiper address is shifted twice when preparing the SPI
> > > command in mcp4131_write_raw().
> > >
> > > The address is already shifted when assigned to the local variable
> > > "address", but is then shifted again when written to data->buf[0].
> > > This results in an incorrect command being sent to the device and
> > > breaks wiper writes to the second channel.
> > >
> > > Remove the second shift and use the pre-shifted address directly
> > > when composing the SPI transfer.
> > >
> > > Signed-off-by: Lukas Schmid <lukas.schmid@netcube.li>
> >
> > Hi Lukas,
> >
> > Good find.
> > Needs a fixes tag though so that we can know how far to backport it.
> > looks like this one goes all the way, so I'll just reply here and
> > pick this up in a minute once my email reaches lore.
> >
> > Fixes: 22d199a53910 ("iio: potentiometer: add driver for Microchip
> > MCP413X/414X/415X/416X/423X/424X/425X/426X")
> I picked it up by hand. A few things to note for next time.
> If you do add RESEND then inside the [] so that the tooling maintainers
> tend to use to pick stuff up (b4 / git am etc) doesn't included the
> RESEND [PATCH v1] in the title of the commit.
>
> Also, if you resend, please include a comment below the --- on why you
> did so.
>
> Now applied to my local tree as I'll be rebasing the fixes branch after
> the release next weekend and am not planning to do a pull request before
> then.
>
Hi Jonathan,
thank you for your hints. Will make sure to follow them next time.
Best regards,
Lukas
> Thanks,
>
> Jonathan
>
> > Thanks,
> >
> > Jonathan
> >
> > > ---
> > >
> > > drivers/iio/potentiometer/mcp4131.c | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/drivers/iio/potentiometer/mcp4131.c
> > > b/drivers/iio/potentiometer/mcp4131.c index ad082827aad5..56c9111ef5e8
> > > 100644
> > > --- a/drivers/iio/potentiometer/mcp4131.c
> > > +++ b/drivers/iio/potentiometer/mcp4131.c
> > > @@ -221,7 +221,7 @@ static int mcp4131_write_raw(struct iio_dev
> > > *indio_dev,
> > >
> > > mutex_lock(&data->lock);
> > >
> > > - data->buf[0] = address << MCP4131_WIPER_SHIFT;
> > > + data->buf[0] = address;
> > >
> > > data->buf[0] |= MCP4131_WRITE | (val >> 8);
> > > data->buf[1] = val & 0xFF; /* 8 bits here */
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-02-02 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-02 20:15 Lukas Schmid
2026-02-02 20:29 ` Jonathan Cameron
2026-02-02 20:34 ` Jonathan Cameron
2026-02-02 20:59 ` Lukas Schmid [this message]
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=4588657.ElGaqSPkdT@lukas-hpz440workstation \
--to=lukas.schmid@netcube.li \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.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
all inboxes | Powered by JetHome®