From: Jonathan Cameron <jic23@kernel.org>
To: Himanshu Jha <himanshujha199640@gmail.com>
Cc: Mike Looijmans <mike.looijmans@topic.nl>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
dpfrey@gmail.com, colin.king@canonical.com
Subject: Re: [PATCH] iio/chemical/bme680: Fix SPI read interface
Date: Wed, 20 Feb 2019 11:22:34 +0000 [thread overview]
Message-ID: <20190220112234.1e42d810@archlinux> (raw)
In-Reply-To: <20190216112722.GA28619@himanshu-Vostro-3559>
..
> > Report temperature in millidegrees Celcius instead of degrees.
>
> Jonathan, I didn't know about this but is there any rationale to report
> in millidegress ?
Misguided attempt in the early days of IIO to match hwmon units.
Sadly it is now the ABI and hence 'unfixable'. Same odd units
for voltage and current + a few others that date back to those
days. A big oops. There are some other non obvious bits and
pieces so should always check the ABI docs which should be near
complete.
>
> I was under the impression that degC is the standard and you would
> always want you Fitbit/Smart watch to report in degC. Ofcourse,
> userspace program can convert millideg -> degC
next prev parent reply other threads:[~2019-02-20 11:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 13:47 [PATCH] iio/chemical/bme680: Fix SPI read interface Mike Looijmans
2019-02-16 11:27 ` Himanshu Jha
2019-02-18 7:03 ` Mike Looijmans
2019-02-20 11:33 ` Jonathan Cameron
2019-02-20 11:22 ` Jonathan Cameron [this message]
2019-02-21 9:20 ` [PATCH v2] " Mike Looijmans
2019-03-03 16:57 ` Jonathan Cameron
2019-03-06 7:27 ` Mike Looijmans
2019-03-06 7:31 ` [PATCH v3 1/2] iio/chemical/bme680: Report temperature in millidegrees Mike Looijmans
2019-03-09 17:05 ` Jonathan Cameron
2019-03-06 7:31 ` [PATCH v3 2/2] iio/chemical/bme680: Fix SPI read interface Mike Looijmans
2019-03-09 17:28 ` Jonathan Cameron
2019-03-16 10:24 ` Himanshu Jha
2019-03-16 13:00 ` Mike Looijmans
2019-03-17 9:48 ` Himanshu Jha
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=20190220112234.1e42d810@archlinux \
--to=jic23@kernel.org \
--cc=colin.king@canonical.com \
--cc=dpfrey@gmail.com \
--cc=himanshujha199640@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.looijmans@topic.nl \
--cc=pmeerw@pmeerw.net \
/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.