From: Jonathan Cameron <jic23@kernel.org>
To: Mitja Spes <mitja@lxnav.com>
Cc: "Lars-Peter Clausen" <lars@metafoo.de>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"Lee Jones" <lee.jones@linaro.org>,
"Jérôme Pouiller" <jerome.pouiller@silabs.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Tomasz Duszynski" <tduszyns@gmail.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] iio: pressure: ms5611: fixed value compensation bug
Date: Sun, 23 Oct 2022 12:06:34 +0100 [thread overview]
Message-ID: <20221023120634.0dda4b5f@jic23-huawei> (raw)
In-Reply-To: <20221021135827.1444793-2-mitja@lxnav.com>
On Fri, 21 Oct 2022 15:58:20 +0200
Mitja Spes <mitja@lxnav.com> wrote:
> When using multiple instances of this driver the compensation PROM was
> overwritten by the last initialized sensor. Now each sensor has own PROM
> storage.
>
> Signed-off-by: Mitja Spes <mitja@lxnav.com>
Fixes tag?
I think this is one we will want to backport.
> ---
> drivers/iio/pressure/ms5611.h | 12 +++----
> drivers/iio/pressure/ms5611_core.c | 51 ++++++++++++++++--------------
> 2 files changed, 31 insertions(+), 32 deletions(-)
>
> diff --git a/drivers/iio/pressure/ms5611.h b/drivers/iio/pressure/ms5611.h
> index cbc9349c342a..550b75b7186f 100644
> --- a/drivers/iio/pressure/ms5611.h
> +++ b/drivers/iio/pressure/ms5611.h
> @@ -25,13 +25,6 @@ enum {
> MS5607,
> };
>
> -struct ms5611_chip_info {
> - u16 prom[MS5611_PROM_WORDS_NB];
> -
> - int (*temp_and_pressure_compensate)(struct ms5611_chip_info *chip_info,
> - s32 *temp, s32 *pressure);
> -};
> -
> /*
> * OverSampling Rate descriptor.
> * Warning: cmd MUST be kept aligned on a word boundary (see
> @@ -50,12 +43,15 @@ struct ms5611_state {
> const struct ms5611_osr *pressure_osr;
> const struct ms5611_osr *temp_osr;
>
> + u16 prom[MS5611_PROM_WORDS_NB];
> +
> int (*reset)(struct ms5611_state *st);
> int (*read_prom_word)(struct ms5611_state *st, int index, u16 *word);
> int (*read_adc_temp_and_pressure)(struct ms5611_state *st,
> s32 *temp, s32 *pressure);
>
> - struct ms5611_chip_info *chip_info;
> + int (*compensate_temp_and_pressure)(struct ms5611_state *st, s32 *temp,
> + s32 *pressure);
> struct regulator *vdd;
> };
>
> diff --git a/drivers/iio/pressure/ms5611_core.c b/drivers/iio/pressure/ms5611_core.c
> index 717521de66c4..c564a1d6cafe 100644
> --- a/drivers/iio/pressure/ms5611_core.c
> +++ b/drivers/iio/pressure/ms5611_core.c
> @@ -85,7 +85,7 @@ static int ms5611_read_prom(struct iio_dev *indio_dev)
> struct ms5611_state *st = iio_priv(indio_dev);
>
> for (i = 0; i < MS5611_PROM_WORDS_NB; i++) {
> - ret = st->read_prom_word(st, i, &st->chip_info->prom[i]);
> + ret = st->read_prom_word(st, i, &st->prom[i]);
> if (ret < 0) {
> dev_err(&indio_dev->dev,
> "failed to read prom at %d\n", i);
> @@ -93,7 +93,7 @@ static int ms5611_read_prom(struct iio_dev *indio_dev)
> }
> }
>
> - if (!ms5611_prom_is_valid(st->chip_info->prom, MS5611_PROM_WORDS_NB)) {
> + if (!ms5611_prom_is_valid(st->prom, MS5611_PROM_WORDS_NB)) {
> dev_err(&indio_dev->dev, "PROM integrity check failed\n");
> return -ENODEV;
> }
> @@ -114,21 +114,20 @@ static int ms5611_read_temp_and_pressure(struct iio_dev *indio_dev,
> return ret;
> }
>
> - return st->chip_info->temp_and_pressure_compensate(st->chip_info,
> - temp, pressure);
> + return st->compensate_temp_and_pressure(st, temp, pressure);
> }
>
> -static int ms5611_temp_and_pressure_compensate(struct ms5611_chip_info *chip_info,
> +static int ms5611_temp_and_pressure_compensate(struct ms5611_state *st,
> s32 *temp, s32 *pressure)
> {
> s32 t = *temp, p = *pressure;
> s64 off, sens, dt;
>
> - dt = t - (chip_info->prom[5] << 8);
> - off = ((s64)chip_info->prom[2] << 16) + ((chip_info->prom[4] * dt) >> 7);
> - sens = ((s64)chip_info->prom[1] << 15) + ((chip_info->prom[3] * dt) >> 8);
> + dt = t - (st->prom[5] << 8);
> + off = ((s64)st->prom[2] << 16) + ((st->prom[4] * dt) >> 7);
> + sens = ((s64)st->prom[1] << 15) + ((st->prom[3] * dt) >> 8);
>
> - t = 2000 + ((chip_info->prom[6] * dt) >> 23);
> + t = 2000 + ((st->prom[6] * dt) >> 23);
> if (t < 2000) {
> s64 off2, sens2, t2;
>
> @@ -154,17 +153,17 @@ static int ms5611_temp_and_pressure_compensate(struct ms5611_chip_info *chip_inf
> return 0;
> }
>
> -static int ms5607_temp_and_pressure_compensate(struct ms5611_chip_info *chip_info,
> +static int ms5607_temp_and_pressure_compensate(struct ms5611_state *st,
> s32 *temp, s32 *pressure)
> {
> s32 t = *temp, p = *pressure;
> s64 off, sens, dt;
>
> - dt = t - (chip_info->prom[5] << 8);
> - off = ((s64)chip_info->prom[2] << 17) + ((chip_info->prom[4] * dt) >> 6);
> - sens = ((s64)chip_info->prom[1] << 16) + ((chip_info->prom[3] * dt) >> 7);
> + dt = t - (st->prom[5] << 8);
> + off = ((s64)st->prom[2] << 17) + ((st->prom[4] * dt) >> 6);
> + sens = ((s64)st->prom[1] << 16) + ((st->prom[3] * dt) >> 7);
>
> - t = 2000 + ((chip_info->prom[6] * dt) >> 23);
> + t = 2000 + ((st->prom[6] * dt) >> 23);
> if (t < 2000) {
> s64 off2, sens2, t2, tmp;
>
> @@ -342,15 +341,6 @@ static int ms5611_write_raw(struct iio_dev *indio_dev,
>
> static const unsigned long ms5611_scan_masks[] = {0x3, 0};
>
> -static struct ms5611_chip_info chip_info_tbl[] = {
> - [MS5611] = {
> - .temp_and_pressure_compensate = ms5611_temp_and_pressure_compensate,
> - },
> - [MS5607] = {
> - .temp_and_pressure_compensate = ms5607_temp_and_pressure_compensate,
> - }
> -};
> -
> static const struct iio_chan_spec ms5611_channels[] = {
> {
> .type = IIO_PRESSURE,
> @@ -433,7 +423,20 @@ int ms5611_probe(struct iio_dev *indio_dev, struct device *dev,
> struct ms5611_state *st = iio_priv(indio_dev);
>
> mutex_init(&st->lock);
> - st->chip_info = &chip_info_tbl[type];
> +
> + switch (type) {
> + case MS5611:
> + st->compensate_temp_and_pressure =
> + ms5611_temp_and_pressure_compensate;
> + break;
> + case MS5607:
> + st->compensate_temp_and_pressure =
> + ms5607_temp_and_pressure_compensate;
> + break;
> + default:
> + return -EINVAL;
> + }
> +
> st->temp_osr =
> &ms5611_avail_temp_osr[ARRAY_SIZE(ms5611_avail_temp_osr) - 1];
> st->pressure_osr =
next prev parent reply other threads:[~2022-10-23 11:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 13:58 [PATCH v2 0/3] ms5611 sensor value bug fix; dt-binding fix Mitja Spes
2022-10-21 13:58 ` [PATCH v2 1/3] iio: pressure: ms5611: fixed value compensation bug Mitja Spes
2022-10-23 11:06 ` Jonathan Cameron [this message]
2022-10-24 6:37 ` Mitja Špes
2022-10-21 13:58 ` [PATCH v2 2/3] iio: pressure: ms5611: changed hardcoded SPI speed to value limited Mitja Spes
2022-10-21 15:32 ` Marcus Folkesson
2022-10-23 11:10 ` Jonathan Cameron
2022-10-24 6:46 ` Mitja Špes
2022-10-23 11:12 ` Jonathan Cameron
2022-10-24 9:05 ` Marcus Folkesson
2022-10-21 13:58 ` [PATCH v2 3/3] dt-bindings: iio: pressure: meas,ms5611: add max SPI frequency to the example Mitja Spes
2022-10-21 14:08 ` Krzysztof Kozlowski
2022-10-23 11:14 ` Jonathan Cameron
2022-10-29 11:40 ` [PATCH v2 0/3] ms5611 sensor value bug fix; dt-binding fix 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=20221023120634.0dda4b5f@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jerome.pouiller@silabs.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mitja@lxnav.com \
--cc=robh+dt@kernel.org \
--cc=tduszyns@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).