linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Andreas Klinger <ak@it-klinger.de>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	bgolaszewski@baylibre.com, linus.walleij@linaro.org,
	tglx@linutronix.de, allison@lohutok.net,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] iio: bmp280: fix compensation of humidity
Date: Sun, 10 May 2020 10:52:36 +0100	[thread overview]
Message-ID: <20200510105236.241eee37@archlinux> (raw)
In-Reply-To: <20200504181033.GA15745@arbad>

On Mon, 4 May 2020 20:10:34 +0200
Andreas Klinger <ak@it-klinger.de> wrote:

> Limit the output of humidity compensation to the range between 0 and 100
> percent.
> 
> Depending on the calibration parameters of the individual sensor it
> happens, that a humidity above 100 percent or below 0 percent is
> calculated, which don't make sense in terms of relative humidity.
> 
> Add a clamp to the compensation formula as described in the datasheet of
> the sensor in chapter 4.2.3.
> 
> Although this clamp is documented, it was never in the driver of the
> kernel.
> 
> It depends on the circumstances (calibration parameters, temperature,
> humidity) if one can see a value above 100 percent without the clamp.
> The writer of this patch was working with this type of sensor without
> noting this error. So it seems to be a rare event when this bug occures.
> 
> Signed-off-by: Andreas Klinger <ak@it-klinger.de>

On basis of description I'm going to take this the slow way (next merge
window).  If you want it backported to stable I don't mind but I haven't
marked it as such so you'll have to request it explicitly after the
patch is in Linus' tree.  It's reasonably likely the scripts will
pick this one up anyway though...

Thanks,

Jonathan

> ---
> 
> Change to v2:
> Thanks to the review of Jonathan a more descriptive commit message is
> added.
> 
> Change to v1:
> Thanks to Tomasz for suggesting the easier to use function clamp_val()
> which is now used.
> 
>  drivers/iio/pressure/bmp280-core.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/iio/pressure/bmp280-core.c b/drivers/iio/pressure/bmp280-core.c
> index 29c209cc1108..297ee2205bf6 100644
> --- a/drivers/iio/pressure/bmp280-core.c
> +++ b/drivers/iio/pressure/bmp280-core.c
> @@ -271,6 +271,8 @@ static u32 bmp280_compensate_humidity(struct bmp280_data *data,
>  		+ (s32)2097152) * calib->H2 + 8192) >> 14);
>  	var -= ((((var >> 15) * (var >> 15)) >> 7) * (s32)calib->H1) >> 4;
>  
> +	var = clamp_val(var, 0, 419430400);
> +
>  	return var >> 12;
>  };
>  


      reply	other threads:[~2020-05-10  9:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 18:10 [PATCH v3] iio: bmp280: fix compensation of humidity Andreas Klinger
2020-05-10  9:52 ` 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=20200510105236.241eee37@archlinux \
    --to=jic23@kernel.org \
    --cc=ak@it-klinger.de \
    --cc=allison@lohutok.net \
    --cc=bgolaszewski@baylibre.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=tglx@linutronix.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).