From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: dimitri.fedrau@liebherr.com
Cc: "Javier Carrasco" <javier.carrasco.cruz@gmail.com>,
"Li peiyu" <579lpy@gmail.com>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Dimitri Fedrau" <dima.fedrau@gmail.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
"Chris Lesiak" <chris.lesiak@licorbio.com>
Subject: Re: [PATCH 1/2] iio: humditiy: hdc3020: fix units for temperature and humidity measurement
Date: Thu, 21 Aug 2025 18:44:25 +0300 [thread overview]
Message-ID: <aKc-2WHDTtGcXmCJ@smile.fi.intel.com> (raw)
In-Reply-To: <20250821-hdc3020-units-fix-v1-1-6ab0bc353c5e@liebherr.com>
On Thu, Aug 21, 2025 at 05:23:54PM +0200, Dimitri Fedrau via B4 Relay wrote:
> From: Dimitri Fedrau <dimitri.fedrau@liebherr.com>
>
> According to the ABI the units after application of scale and offset are
> milli degrees for temperature measurements and milli percent for relative
> humidity measurements. Change scale factor to fix this issue.
...
> if (chan->type == IIO_TEMP)
> - *val = 175;
> + *val = 175000;
> else
> - *val = 100;
> + *val = 100000;
Perhaps use " * MILL" uin both cases?
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-08-21 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 15:23 [PATCH 0/2] iio: humditiy: hdc3020: fix units Dimitri Fedrau
2025-08-21 15:23 ` Dimitri Fedrau via B4 Relay
2025-08-21 15:23 ` [PATCH 1/2] iio: humditiy: hdc3020: fix units for temperature and humidity measurement Dimitri Fedrau
2025-08-21 15:23 ` Dimitri Fedrau via B4 Relay
2025-08-21 15:44 ` Andy Shevchenko [this message]
2025-08-21 15:45 ` Andy Shevchenko
2025-08-22 12:36 ` Dimitri Fedrau
2025-08-21 15:23 ` [PATCH 2/2] iio: humditiy: hdc3020: fix units for thresholds and hysteresis Dimitri Fedrau
2025-08-21 15:23 ` Dimitri Fedrau via B4 Relay
2025-08-24 12:36 ` Javier Carrasco
2025-08-28 7:43 ` 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=aKc-2WHDTtGcXmCJ@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=579lpy@gmail.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=andy@kernel.org \
--cc=chris.lesiak@licorbio.com \
--cc=dima.fedrau@gmail.com \
--cc=dimitri.fedrau@liebherr.com \
--cc=dlechner@baylibre.com \
--cc=javier.carrasco.cruz@gmail.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.