[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZXS/9+lcD+/ptfKr@abdel>
Date: Sat, 9 Dec 2023 14:28:55 -0500
From: Abdel Alkuor <alkuor@...il.com>
To: Jonathan Cameron <jic23@...nel.org>
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 Wed, Dec 06, 2023 at 05:40:50PM +0000, Jonathan Cameron wrote:
> On Mon, 4 Dec 2023 21:19:22 -0500
> Abdel Alkuor <alkuor@...il.com> wrote:
>
Hi Jonathan,
> 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?
No specific reason. I thought IIO is the de facto for such sensors. I'll
use hwmon instead.
Thanks the clarification.
Abdel
Powered by blists - more mailing lists