[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231206174050.12ad1c98@jic23-huawei>
Date: Wed, 6 Dec 2023 17:40:50 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: Abdel Alkuor <alkuor@...il.com>
Cc: Conor Dooley <conor@...nel.org>, krzysztof.kozlowski+dt@...aro.org,
robh+dt@...nel.org, lars@...afoo.de, conor+dt@...nel.org,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org,
devicetree@...r.kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: temperature: Add AMS AS6200
On Mon, 4 Dec 2023 21:19:22 -0500
Abdel Alkuor <alkuor@...il.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
Powered by blists - more mailing lists