From: Jonathan Cameron <jic23@kernel.org>
To: Zhu Jun <zhujun2@cmss.chinamobile.com>
Cc: dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: potentiostat: lmp91000: Handle configuration write errors
Date: Fri, 13 Nov 2026 01:23:32 +0000 [thread overview]
Message-ID: <20261113012332.1be06bf9@jic23-hlaptop> (raw)
In-Reply-To: <20261112071747.154626-1-zhujun2@cmss.chinamobile.com>
On Thu, 12 Nov 2026 15:17:47 +0800
Zhu Jun <zhujun2@cmss.chinamobile.com> wrote:
> lmp91000_read_config() ignores errors when unlocking and programming
> the TIA and reference registers. Probe can then succeed even though
> the hardware configuration does not match the parameters used to
> interpret measurements.
>
> Check the configuration writes and return the first error. After a
> successful unlock, attempt to restore write protection even if a
> configuration write fails, and report a relock failure as well.
>
> Fixes: 67e17300dc1d ("iio: potentiostat: add LMP91000 support")
> Signed-off-by: Zhu Jun <zhujun2@cmss.chinamobile.com>
Minor comment on the approach used inline.
Thanks,
Jonathan
> ---
> drivers/iio/potentiostat/lmp91000.c | 20 +++++++++++++-------
> 1 file changed, 13 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/iio/potentiostat/lmp91000.c b/drivers/iio/potentiostat/lmp91000.c
> index 00cb3fea97ca..4a29fe627af7 100644
> --- a/drivers/iio/potentiostat/lmp91000.c
> +++ b/drivers/iio/potentiostat/lmp91000.c
> @@ -205,7 +205,7 @@ static int lmp91000_read_config(struct lmp91000_data *data)
> {
> struct device *dev = data->dev;
> unsigned int reg, val;
> - int i, ret;
> + int i, ret, lock_ret;
>
> ret = device_property_read_u32(dev, "ti,tia-gain-ohm", &val);
> if (ret) {
> @@ -250,13 +250,19 @@ static int lmp91000_read_config(struct lmp91000_data *data)
> return ret;
> }
>
> - regmap_write(data->regmap, LMP91000_REG_LOCK, 0);
> - regmap_write(data->regmap, LMP91000_REG_TIACN, reg);
> - regmap_write(data->regmap, LMP91000_REG_REFCN,
> - LMP91000_REG_REFCN_EXT_REF | LMP91000_REG_REFCN_50_ZERO);
> - regmap_write(data->regmap, LMP91000_REG_LOCK, 1);
> + ret = regmap_write(data->regmap, LMP91000_REG_LOCK, 0);
> + if (ret)
> + return ret;
>
> - return 0;
> + ret = regmap_write(data->regmap, LMP91000_REG_TIACN, reg);
> + if (!ret)
> + ret = regmap_write(data->regmap, LMP91000_REG_REFCN,
> + LMP91000_REG_REFCN_EXT_REF | LMP91000_REG_REFCN_50_ZERO);
> +
> + /* Restore write protection even if programming the registers failed. */
> + lock_ret = regmap_write(data->regmap, LMP91000_REG_LOCK, 1);
I'm never a fan of flows where we pick between ret values. tHey make for very messy
code. It is easier to read with one line effectively duplicated.
ret = regmap_write(data->regmap, LMP91000_REG_LOCK, 0);
if (ret)
return ret;
ret = regmap_write(data->regmap, LMP91000_REG_TIACN, reg);
if (ret)
goto unlock;
ret = regmap_write(data->regmap, LMP91000_REG_REFCN,
LMP91000_REG_REFCN_EXT_REF | LMP91000_REG_REFCN_50_ZERO);
if (ret)
goto unlock;
return regmap_write(data->regmap, LMP91000_REG_LOCK, 1);
unlock:
regmap_write(data->regmap, LMP91000_REG_LOCK, 1);
return ret;
> +
> + return ret ? ret : lock_ret;
> }
>
> static int lmp91000_buffer_cb(const void *val, void *private)
prev parent reply other threads:[~2026-11-13 1:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 7:17 Zhu Jun
2026-11-12 16:03 ` Andy Shevchenko
2026-11-13 1:23 ` Jonathan Cameron [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=20261113012332.1be06bf9@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=zhujun2@cmss.chinamobile.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®