From: Guenter Roeck <linux@roeck-us.net>
To: Jonathan Cameron <jic23@kernel.org>,
Marius Cristea <marius.cristea@microchip.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, jdelvare@suse.com,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 0/2] Add support for Microchip EMC1812
Date: Tue, 23 Sep 2025 19:11:05 -0700 [thread overview]
Message-ID: <a97486df-9f15-4280-8cb3-d77f4cf223df@roeck-us.net> (raw)
In-Reply-To: <20250920123340.1b1d03be@jic23-huawei>
On 9/20/25 04:33, Jonathan Cameron wrote:
> On Wed, 17 Sep 2025 15:21:56 +0300
> Marius Cristea <marius.cristea@microchip.com> wrote:
>
>> This is the iio driver for EMC1812/13/14/15/33 multichannel Low-Voltage
>> Remote Diode Sensor Family. The chips in the family have one internal
>> and different numbers of external channels, ranging from 1 (EMC1812) to
>> 4 channels (EMC1815).
>> Reading diodes in anti-parallel connection is supported by EMC1814, EMC1815
>> and EMC1833.
>>
>> Current version of driver does not support interrupts, events and data
>> buffering.
> Hi Marius,
>
> For a temperature monitoring device like this, the opening question is
> always why not HWMON?
>
> There are various reasons we have temp sensors in IIO but mostly they are not
> described as being monitors and this one is.
>
> IIO may well be the right choice for this part, but good to lay out your
> reasoning and +CC the hwmon list and maintainers. There is an emc1403
> driver already in hwmon, so perhaps compare and contrast with that.
>
> I've +CC Jean, Guenter and list to save sending a v2 just to do that.
>
At first glance it looks like the series is (mostly ?) register compatible
to the chips supported by the emc1403 driver, so it should be straightforward
to add support for the emc180x series to that driver.
Guenter
next prev parent reply other threads:[~2025-09-24 2:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 12:21 [PATCH 0/2] Add support for Microchip EMC1812 Marius Cristea
2025-09-17 12:21 ` [PATCH 1/2] dt-bindings: iio: temperature: add support for EMC1812 Marius Cristea
2025-09-17 14:31 ` Rob Herring (Arm)
2025-09-17 23:34 ` David Lechner
2025-09-25 14:27 ` Marius.Cristea
2025-09-17 12:21 ` [PATCH 2/2] " Marius Cristea
2025-09-18 3:07 ` kernel test robot
2025-09-20 11:51 ` Jonathan Cameron
2025-09-20 15:05 ` David Lechner
2025-09-23 5:31 ` Dan Carpenter
2025-09-17 13:25 ` [PATCH 0/2] Add support for Microchip EMC1812 David Lechner
2025-09-17 13:30 ` Marius.Cristea
2025-09-17 13:38 ` David Lechner
2025-09-20 11:33 ` Jonathan Cameron
2025-09-24 2:11 ` Guenter Roeck [this message]
2025-09-25 9:09 ` Marius.Cristea
2025-09-25 14:32 ` Guenter Roeck
2025-09-27 15:04 ` Jonathan Cameron
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=a97486df-9f15-4280-8cb3-d77f4cf223df@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jdelvare@suse.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=nuno.sa@analog.com \
--cc=robh@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