[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e566ee56-523c-4cfd-999d-1cd9ca8eb7a6@roeck-us.net>
Date: Fri, 8 Nov 2024 07:49:54 -0800
From: Guenter Roeck <linux@...ck-us.net>
To: Jonathan Cameron <Jonathan.Cameron@...wei.com>,
Frank Li <Frank.Li@....com>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Jonathan Cameron <jic23@...nel.org>,
Lars-Peter Clausen <lars@...afoo.de>, Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
Fabio Estevam <festevam@...il.com>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
imx@...ts.linux.dev, linux-arm-kernel@...ts.infradead.org,
Carlos Song <carlos.song@....com>, Clark Wang <xiaoning.wang@....com>,
Jean Delvare <jdelvare@...e.com>, linux-hwmon@...r.kernel.org
Subject: Re: [PATCH 0/3] iio: temperature: Add support for P3T1085
On 11/8/24 07:28, Jonathan Cameron wrote:
> On Thu, 07 Nov 2024 18:02:26 -0500
> Frank Li <Frank.Li@....com> wrote:
>
>> Add basic function support for P3T1085 temperature sensor.
>> - Add binding doc trivial.yaml
>> - Add basic read temperature driver
> Hi Frank,
>
> For a simple temperature sensor the usual question is why IIO rather
> than hwmon?
>
From looking into the datasheet, this is a chip which will be typically
used for hardware monitoring.
> Previous reasons have been:
> - Very high performmance / accuracy part (i.e. expensive)
0.25 Hz ... 16 Hz sampling rate. No.
> - Remote temperature so not typically hw monitoring.
Local only.
> - Same silicon with a more complex sensor (typically humidity or similar).
>
No.
It looks like the I2C part of the chip is is compatible to TMP108, so
another question would be why to implement a new driver in the first place.
Guenter
Powered by blists - more mailing lists