From: Vasileios Amoiridis <vassilisamir@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Vasileios Amoiridis <vassilisamir@gmail.com>,
lars@metafoo.de, andriy.shevchenko@linux.intel.com,
ang.iglesiasg@gmail.com, mazziesaccount@gmail.com,
ak@it-klinger.de, petre.rodan@subdimension.ro,
linus.walleij@linaro.org, phil@raspberrypi.com, 579lpy@gmail.com,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 4/6] iio: pressure: Simplify and make more clear temperature readings
Date: Thu, 14 Mar 2024 21:17:18 +0100 [thread overview]
Message-ID: <20240314201718.GD1964894@vamoiridPC> (raw)
In-Reply-To: <20240314150959.585367b5@jic23-huawei>
On Thu, Mar 14, 2024 at 03:09:59PM +0000, Jonathan Cameron wrote:
> On Wed, 13 Mar 2024 18:40:05 +0100
> Vasileios Amoiridis <vassilisamir@gmail.com> wrote:
>
> > The read_press/read_humid functions need the updated t_fine value
> > in order to calculate the current pressure/humidity. Temperature
> > reads should be removed from the read_press/read_humid functions
> > and should be placed in the oneshot captures before the pressure
> > and humidity reads. This makes the code more intuitive.
> >
> > Signed-off-by: Vasileios Amoiridis <vassilisamir@gmail.com>
>
> To me this makes the use of these calls less obvious than they were
> previously. The calls are made close to where t_fine is used and
> don't have to go via the indirection of chip_info.
>
> So I disagree. I think this change makes the code a lot less
> clear.
>
This was mainly driven by the fact that I wanted to avoid reading
the temperature 3 times in case temp, press and humid are enabled
and there are consecutive buffer readings. But thank you for the
proposal I really appreciate it!
Best regards,
Vasilis
> The only improvement I can readily see would be to move the
> temperature read into the compensation functions themselves, possibly
> removing t_fine from data and having a function that reads everything
> relevant to computing it directly but doesn't do the maths to get
> a temperature reading. That can be reused in bmp280_compensate_temp()
>
> Something along lines of.
>
> static s32 bmp280_calc_tfine(struct bmp280_calib *calib, s32 adc_temp)
> {
> s32 var1, var2;
>
> var1 = (((adc_temp >> 3) - ((s32)calib->T1 << 1)) *
> ((s32)calib->T2)) >> 11;
> var2 = (((((adc_temp >> 4) - ((s32)calib->T1)) *
> ((adc_temp >> 4) - ((s32)calib->T1))) >> 12) *
> ((s32)calib->T3)) >> 14;
> return var1 + var2;
> }
>
> static int bmp280_read_temp_raw(struct bmp280_data *data,
> s32 *raw)
> {
> s32 adc_temp;
> int ret;
>
> ret = regmap_bulk_read(data->regmap, BMP280_REG_TEMP_MSB,
> data->buf, sizeof(data->buf));
> if (ret < 0) {
> dev_err(data->dev, "failed to read temperature\n");
> return ret;
> }
>
> adc_temp = FIELD_GET(BMP280_MEAS_TRIM_MASK, get_unaligned_be24(data->buf));
> if (adc_temp == BMP280_TEMP_SKIPPED) {
> /* reading was skipped */
> dev_err(data->dev, "reading temperature skipped\n");
> return -EIO;
> }
> *raw = adc_temp;
>
> return 0;
> }
> static int bmp280_get_t_fine(.., s32 *t_fine)
> {
> s32 adc_temp, comp_temp;
> s32 t_fine;
> int ret;
>
> ret = bmp280_read_temp_raw(data, &adc_temp;
> if (ret)
> return ret;
>
> *t_fine = bmp280_calc_tfine(&data->calib.bmp280, adc_temp);
> return 0;
> }
>
> static int bmp280_read_temp(struct bmp280_data *data, s32 *temp)
> {
> int ret;
> s32 t_fine;
>
> ret = bmp280_get_t_fine(data, &t_fine);
> if (ret)
> return ret;
>
> *temp = (t_fine * 5 + 128) / 256;
> //division rather than shift as then it's obvious what the 128 is there for
> return 0;
> }
>
> Now you have a nice function to get you t_fine which is all you want in some
> of these paths. Call it directly where it is needed instead of as
> a side effect of a temperature read.
>
>
>
> > ---
> > drivers/iio/pressure/bmp280-core.c | 38 ++++++++++++++----------------
> > 1 file changed, 18 insertions(+), 20 deletions(-)
> >
> > diff --git a/drivers/iio/pressure/bmp280-core.c b/drivers/iio/pressure/bmp280-core.c
> > index 6d7734f867bc..377e90d9e5a2 100644
> > --- a/drivers/iio/pressure/bmp280-core.c
> > +++ b/drivers/iio/pressure/bmp280-core.c
> > @@ -404,11 +404,6 @@ static u32 bmp280_read_press(struct bmp280_data *data)
> > s32 adc_press;
> > int ret;
> >
> > - /* Read and compensate temperature so we get a reading of t_fine. */
> > - ret = bmp280_read_temp(data);
> > - if (ret < 0)
> > - return ret;
> > -
> > ret = regmap_bulk_read(data->regmap, BMP280_REG_PRESS_MSB,
> > data->buf, sizeof(data->buf));
> > if (ret < 0) {
> > @@ -433,11 +428,6 @@ static u32 bmp280_read_humid(struct bmp280_data *data)
> > s32 adc_humidity;
> > int ret;
> >
> > - /* Read and compensate temperature so we get a reading of t_fine. */
> > - ret = bmp280_read_temp(data);
> > - if (ret < 0)
> > - return ret;
> > -
> > ret = regmap_bulk_read(data->regmap, BMP280_REG_HUMIDITY_MSB,
> > &data->be16, sizeof(data->be16));
> > if (ret < 0) {
> > @@ -470,12 +460,21 @@ static int bmp280_read_raw(struct iio_dev *indio_dev,
> > case IIO_CHAN_INFO_PROCESSED:
> > switch (chan->type) {
> > case IIO_HUMIDITYRELATIVE:
> > + /* Read temperature to update the t_fine value */
> > + data->chip_info->read_temp(data);
> > ret = data->chip_info->read_humid(data);
> > *val = data->chip_info->humid_coeffs[0] * ret;
> > *val2 = data->chip_info->humid_coeffs[1];
> > ret = IIO_VAL_FRACTIONAL;
> > break;
> > case IIO_PRESSURE:
> > + /*
> > + * Read temperature to update the t_fine value.
> > + * BMP5xx devices do this in hardware, so skip it.
> > + */
> > + if (strcmp(indio_dev->name, "bmp580"))
> > + data->chip_info->read_temp(data);
> > +
> > ret = data->chip_info->read_press(data);
> > *val = data->chip_info->press_coeffs[0] * ret;
> > *val2 = data->chip_info->press_coeffs[1];
> > @@ -500,10 +499,19 @@ static int bmp280_read_raw(struct iio_dev *indio_dev,
> > case IIO_CHAN_INFO_RAW:
> > switch (chan->type) {
> > case IIO_HUMIDITYRELATIVE:
> > + /* Read temperature to update the t_fine value */
> > + data->chip_info->read_temp(data);
> > *val = data->chip_info->read_humid(data);
> > ret = IIO_VAL_INT;
> > break;
> > case IIO_PRESSURE:
> > + /*
> > + * Read temperature to update the t_fine value.
> > + * BMP5xx devices do this in hardware, so skip it.
> > + */
> > + if (strcmp(indio_dev->name, "bmp580"))
> > + data->chip_info->read_temp(data);
> > +
> > *val = data->chip_info->read_press(data);
> > ret = IIO_VAL_INT;
> > break;
> > @@ -1092,11 +1100,6 @@ static u32 bmp380_read_press(struct bmp280_data *data)
> > s32 adc_press;
> > int ret;
> >
> > - /* Read and compensate for temperature so we get a reading of t_fine */
> > - ret = bmp380_read_temp(data);
> > - if (ret)
> > - return ret;
> > -
> > ret = regmap_bulk_read(data->regmap, BMP380_REG_PRESS_XLSB,
> > data->buf, sizeof(data->buf));
> > if (ret) {
> > @@ -2009,11 +2012,6 @@ static u32 bmp180_read_press(struct bmp280_data *data)
> > s32 adc_press;
> > int ret;
> >
> > - /* Read and compensate temperature so we get a reading of t_fine. */
> > - ret = bmp180_read_temp(data);
> > - if (ret)
> > - return ret;
> > -
> > ret = bmp180_read_adc_press(data, &adc_press);
> > if (ret)
> > return ret;
>
next prev parent reply other threads:[~2024-03-14 20:17 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 17:40 [PATCH v2 0/6] Series to add triggered buffer support to BMP280 driver Vasileios Amoiridis
2024-03-13 17:40 ` [PATCH v2 1/6] iio: pressure: BMP280 core driver headers sorting Vasileios Amoiridis
2024-03-13 17:40 ` [PATCH v2 2/6] iio: pressure: Simplify read_* functions Vasileios Amoiridis
2024-03-13 19:01 ` Andy Shevchenko
2024-03-13 19:22 ` Vasileios Amoiridis
2024-03-13 19:28 ` Andy Shevchenko
2024-03-14 14:32 ` Jonathan Cameron
2024-03-14 19:52 ` Vasileios Amoiridis
2024-03-14 14:38 ` Jonathan Cameron
2024-03-13 17:40 ` [PATCH v3 3/6] iio: pressure: add SCALE and RAW values for channels Vasileios Amoiridis
2024-03-13 19:03 ` Andy Shevchenko
2024-03-13 19:51 ` Vasileios Amoiridis
2024-03-13 20:04 ` Andy Shevchenko
2024-03-13 21:28 ` Vasileios Amoiridis
2024-03-14 10:57 ` vamoirid
2024-03-14 14:46 ` Jonathan Cameron
2024-03-14 20:06 ` Vasileios Amoiridis
2024-03-15 13:11 ` Vasileios Amoiridis
2024-03-16 13:51 ` Jonathan Cameron
2024-03-14 14:48 ` Jonathan Cameron
2024-03-13 17:40 ` [PATCH v2 4/6] iio: pressure: Simplify and make more clear temperature readings Vasileios Amoiridis
2024-03-13 19:04 ` Andy Shevchenko
2024-03-14 14:51 ` Jonathan Cameron
2024-03-14 15:09 ` Jonathan Cameron
2024-03-14 20:17 ` Vasileios Amoiridis [this message]
2024-03-14 23:22 ` Angel Iglesias
2024-03-15 9:05 ` Vasileios Amoiridis
2024-03-15 13:28 ` Angel Iglesias
2024-03-16 14:00 ` Jonathan Cameron
2024-03-13 17:40 ` [PATCH v2 5/6] iio: pressure: Add timestamp and scan_masks for BMP280 driver Vasileios Amoiridis
2024-03-13 18:54 ` Andy Shevchenko
2024-03-13 19:55 ` Vasileios Amoiridis
2024-03-13 17:40 ` [PATCH v2 6/6] iio: pressure: Add triggered buffer support " Vasileios Amoiridis
2024-03-13 18:58 ` Andy Shevchenko
2024-03-13 20:00 ` Vasileios Amoiridis
2024-03-14 15:25 ` Jonathan Cameron
2024-03-14 20:14 ` Vasileios Amoiridis
2024-03-16 14:03 ` 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=20240314201718.GD1964894@vamoiridPC \
--to=vassilisamir@gmail.com \
--cc=579lpy@gmail.com \
--cc=ak@it-klinger.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=ang.iglesiasg@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mazziesaccount@gmail.com \
--cc=petre.rodan@subdimension.ro \
--cc=phil@raspberrypi.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