From: Dimitri Fedrau <dima.fedrau@gmail.com>
To: Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
579lpy@gmail.com, jic23@kernel.org, lars@metafoo.de,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: humidity: hdc3020: add threshold events support
Date: Sat, 3 Feb 2024 15:54:01 +0100 [thread overview]
Message-ID: <20240203145401.GC3727@debian> (raw)
In-Reply-To: <b789eb01-5b5d-4513-88d2-1f14e95969d9@gmail.com>
Am Sat, Feb 03, 2024 at 11:06:02AM +0100 schrieb Javier Carrasco:
> On 03.02.24 10:58, Christophe JAILLET wrote:
> > Le 03/02/2024 à 10:05, Dimitri Fedrau a écrit :
> >> [...]
> >> drivers/iio/humidity/hdc3020.c | 339 +++++++++++++++++++++++++++++++++
> >> 1 file changed, 339 insertions(+)
>
> ...
>
> >> + guard(mutex)(&data->lock);
> >> + switch (chan->type) {
> >> + case IIO_TEMP:
> >> + /*
> >> + * Store truncated temperature threshold into 9 LSBs while
> >> + * keeping the old humidity threshold in the 7 MSBs.
> >> + */
> >> + val = (((val + 45) * 65535 / 175) >> HDC3020_THRESH_TEMP_SHIFT);
> >
> > Why 175?
> > If the span is -40/+120, I guess it should be 160 and if it is -45/+120,
> > 165. No?
> >
> > Maybe something like:
> > #define MIN_TEMP -45 (or -40)
> > #define MAX_TEMP 120
> > in order to avoid hard coded constant?
> >
>
> the 45 and 175 values come from the conversion formula provided in the
> datasheet (page 13), even though the sensor range is from –40°C to 125°C.
>
Will add following constants:
#define MIN_TEMP -40
#define MAX_TEMP 125
It's the supported temperature range by the chip as Javier already
explained. Thanks for finding this.
> >> [...]
Best regards,
Dimitri
next prev parent reply other threads:[~2024-02-03 14:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 9:05 [PATCH] iio: humidity: hdc3020: add threshold events support Dimitri Fedrau
2024-02-03 9:30 ` Javier Carrasco
2024-02-03 14:42 ` Dimitri Fedrau
2024-02-03 15:53 ` Javier Carrasco
2024-02-03 16:08 ` Dimitri Fedrau
2024-02-03 9:58 ` Christophe JAILLET
2024-02-03 10:06 ` Javier Carrasco
2024-02-03 14:54 ` Dimitri Fedrau [this message]
2024-02-03 14:47 ` Dimitri Fedrau
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=20240203145401.GC3727@debian \
--to=dima.fedrau@gmail.com \
--cc=579lpy@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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