From: Sam Winchenbach <swinchenbach@arka.org>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"antoniu.miclaus@analog.com" <antoniu.miclaus@analog.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"Michael.Hennerich@analog.com" <Michael.Hennerich@analog.com>
Subject: RE: Re: iio: filter: admv8818: Force initialization of SDO
Date: Fri, 31 Jan 2025 12:30:25 +0000 [thread overview]
Message-ID: <SA1P110MB10690D050787621F1C96AE70BCE8A@SA1P110MB1069.NAMP110.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20250125122610.4d084c13@jic23-huawei>
> Hi Sam, we shouldn't be seeing the email header in the patch.
>
> I can tidy that up if you can't fix it though.
> >
> > When a weak pull-up is present on the SDO line, regmap_update_bits
> > fails to write both the SOFTRESET and SDOACTIVE bits because it
> > incorrectly reads them as already set.
> >
> > Since the soft reset disables the SDO line, performing a
> > read-modify-write operation on ADI_SPI_CONFIG_A to enable the SDO line
> > doesn't make sense. This change directly writes to the register
> > instead of using regmap_update_bits.
> >
> Sounds like a fix, so could you send an appropriate Fixes tag in a v2 and/or a reply to this email.
Added the fixes tag and submitted as patch v2. Please let me know if there is anything else that is needed.
Thanks.
>
> > Signed-off-by: Sam Winchenbach <swinchenbach@arka.org>
> > ---
> > drivers/iio/filter/admv8818.c | 14 ++++----------
> > 1 file changed, 4 insertions(+), 10 deletions(-)
> >
> > diff --git a/drivers/iio/filter/admv8818.c
> > b/drivers/iio/filter/admv8818.c index 195e58bc4..9cd1eee84 100644
> > --- a/drivers/iio/filter/admv8818.c
> > +++ b/drivers/iio/filter/admv8818.c
> > @@ -577,21 +577,15 @@ static int admv8818_init(struct admv8818_state *st)
> > struct spi_device *spi = st->spi;
> > unsigned int chip_id;
> >
> > - ret = regmap_update_bits(st->regmap, ADMV8818_REG_SPI_CONFIG_A,
> > - ADMV8818_SOFTRESET_N_MSK |
> > - ADMV8818_SOFTRESET_MSK,
> > - FIELD_PREP(ADMV8818_SOFTRESET_N_MSK, 1) |
> > - FIELD_PREP(ADMV8818_SOFTRESET_MSK, 1));
> > + ret = regmap_write(st->regmap, ADMV8818_REG_SPI_CONFIG_A,
> > + ADMV8818_SOFTRESET_N_MSK |
> > + ADMV8818_SOFTRESET_MSK);
> > if (ret) {
> > dev_err(&spi->dev, "ADMV8818 Soft Reset failed.\n");
> > return ret;
> > }
> >
> > - ret = regmap_update_bits(st->regmap, ADMV8818_REG_SPI_CONFIG_A,
> > - ADMV8818_SDOACTIVE_N_MSK |
> > - ADMV8818_SDOACTIVE_MSK,
> > - FIELD_PREP(ADMV8818_SDOACTIVE_N_MSK, 1) |
> > - FIELD_PREP(ADMV8818_SDOACTIVE_MSK, 1));
> > + ret = regmap_write(st->regmap, ADMV8818_REG_SPI_CONFIG_A,
> > + ADMV8818_SDOACTIVE_N_MSK |
> > + ADMV8818_SDOACTIVE_MSK);
> > if (ret) {
> > dev_err(&spi->dev, "ADMV8818 SDO Enable failed.\n");
> > return ret;
prev parent reply other threads:[~2025-01-31 12:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 18:27 [PATCH] " Sam Winchenbach
2025-01-25 12:26 ` Jonathan Cameron
2025-01-31 12:30 ` Sam Winchenbach [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=SA1P110MB10690D050787621F1C96AE70BCE8A@SA1P110MB1069.NAMP110.PROD.OUTLOOK.COM \
--to=swinchenbach@arka.org \
--cc=Michael.Hennerich@analog.com \
--cc=antoniu.miclaus@analog.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@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®