From: Jonathan Cameron <jic23@kernel.org>
To: Abdel Alkuor <alkuor@gmail.com>
Cc: Conor Dooley <conor@kernel.org>,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
lars@metafoo.de, conor+dt@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: temperature: Add AMS AS6200
Date: Wed, 6 Dec 2023 17:40:50 +0000 [thread overview]
Message-ID: <20231206174050.12ad1c98@jic23-huawei> (raw)
In-Reply-To: <ZW6IqoelmMhTgjgW@abdel>
On Mon, 4 Dec 2023 21:19:22 -0500
Abdel Alkuor <alkuor@gmail.com> wrote:
> On Sun, Dec 03, 2023 at 11:24:31AM +0000, Conor Dooley wrote:
> > On Fri, Dec 01, 2023 at 11:16:50PM -0500, Abdel Alkuor wrote:
> > > as6200 is high accuracy temperature sensor of -/+ 0.4C degree
> >
> Hi Conor,
> > Is +/- 0.4 degrees really "high accuracy"?
> >
> That's what the datasheet says :D. I'll remove it.
I'd not noticed this. Why is this an IIO driver rather than an hwmon one?
Mostly we do that only for very high accuracy or weird temperature sensors
(infrared ones for example or things with complex thermocouple handling).
Simpler devices meant for hardware monitoring type applications typically go
in hwmon.
We have the iio to hwmon bridge driver for things that naturally have uses
where IIO features are needed, but which get used for hwmon sometimes.
Not sure this is enough IIO focused though, so perhaps list out why you
think it should be in IIO?
Jonathan
next prev parent reply other threads:[~2023-12-06 17:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 4:16 [PATCH v2 1/2] dt-bindings: iio: temperature: Add AMS AS6200 Abdel Alkuor
2023-12-02 4:16 ` [PATCH v2 2/2] iio: temperature: Add support for " Abdel Alkuor
2023-12-04 13:50 ` Jonathan Cameron
2023-12-05 2:16 ` Abdel Alkuor
2023-12-06 17:36 ` Jonathan Cameron
2023-12-03 11:24 ` [PATCH v2 1/2] dt-bindings: iio: temperature: Add " Conor Dooley
2023-12-05 2:19 ` Abdel Alkuor
2023-12-06 17:40 ` Jonathan Cameron [this message]
2023-12-09 19:28 ` Abdel Alkuor
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=20231206174050.12ad1c98@jic23-huawei \
--to=jic23@kernel.org \
--cc=alkuor@gmail.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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