From: Jonathan Cameron <jic23@kernel.org>
To: Tomasz Duszynski <tduszyns@gmail.com>
Cc: linux-iio@vger.kernel.org, linus.walleij@linaro.org
Subject: Re: [PATCH] iio: pressure: bmp280: fix relative humidity unit
Date: Sun, 3 Jun 2018 15:41:54 +0100 [thread overview]
Message-ID: <20180603154154.0941f5fd@archlinux> (raw)
In-Reply-To: <20180528153859.813-1-tduszyns@gmail.com>
On Mon, 28 May 2018 17:38:59 +0200
Tomasz Duszynski <tduszyns@gmail.com> wrote:
> According to IIO ABI relative humidity reading should be
> returned in milli percent.
>
> This patch addresses that by applying proper scaling and
> returning integer instead of fractional format type specifier.
>
> Signed-off-by: Tomasz Duszynski <tduszyns@gmail.com>
I'll be wanting input from Linus on this as he seems to be the last person
to have taken particular interest in the driver.
> ---
> drivers/iio/pressure/bmp280-core.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/pressure/bmp280-core.c b/drivers/iio/pressure/bmp280-core.c
> index 5ec3e41b65f2..fe87d27779d9 100644
> --- a/drivers/iio/pressure/bmp280-core.c
> +++ b/drivers/iio/pressure/bmp280-core.c
> @@ -415,10 +415,9 @@ static int bmp280_read_humid(struct bmp280_data *data, int *val, int *val2)
> }
> comp_humidity = bmp280_compensate_humidity(data, adc_humidity);
>
> - *val = comp_humidity;
> - *val2 = 1024;
> + *val = comp_humidity * 1000 / 1024;
Why not just *val = *val * 1000 and leave the rest alone?
>
> - return IIO_VAL_FRACTIONAL;
> + return IIO_VAL_INT;
> }
>
> static int bmp280_read_raw(struct iio_dev *indio_dev,
next prev parent reply other threads:[~2018-06-03 14:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 15:38 [PATCH] iio: pressure: bmp280: fix relative humidity unit Tomasz Duszynski
2018-05-30 0:44 ` Matt Ranostay
2018-05-30 1:17 ` Phil Reid
2018-05-30 5:05 ` Matt Ranostay
2018-05-30 7:20 ` Matt Ranostay
2018-05-30 14:23 ` Tomasz Duszynski
2018-05-30 23:31 ` Phil Reid
2018-05-31 1:04 ` Matt Ranostay
2018-05-31 2:06 ` Matt Ranostay
2018-06-03 14:59 ` Jonathan Cameron
2018-06-03 14:45 ` Jonathan Cameron
2018-06-03 14:41 ` Jonathan Cameron [this message]
2018-06-03 14:43 ` 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=20180603154154.0941f5fd@archlinux \
--to=jic23@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=tduszyns@gmail.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;
as well as URLs for NNTP newsgroup(s).