From: <Marius.Cristea@microchip.com>
To: <linux@roeck-us.net>, <jic23@kernel.org>
Cc: <dlechner@baylibre.com>, <linux-hwmon@vger.kernel.org>,
<jdelvare@suse.com>, <nuno.sa@analog.com>,
<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
<robh@kernel.org>, <linux-kernel@vger.kernel.org>,
<andy@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>
Subject: Re: [PATCH 0/2] Add support for Microchip EMC1812
Date: Thu, 25 Sep 2025 09:09:04 +0000 [thread overview]
Message-ID: <e6ab5becf5908d83857fcfd57823ffd259e6db90.camel@microchip.com> (raw)
In-Reply-To: <a97486df-9f15-4280-8cb3-d77f4cf223df@roeck-us.net>
Hi Guenter,
Thank you for the feedback.
On Tue, 2025-09-23 at 19:11 -0700, Guenter Roeck wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> 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
Most of the register address are compatible. The EMC181X is an update
(a newer generation) then the EMC1403.
The biggest improvement is that the EMC18XX has a continuous block of
registers in order to improve the temperature reading (that means some
addresses are overlapping with the older register maps) and a new set
of registers to handle the "Rate Of Change" functionality.
Also the older EMC14XX has some hardcoded configuration/features based
on the part number.
Considering all of the above I consider that the complexity of the
EMC1403 will increase quite a lot without any real benefit and it will
be harder to be maintained.
I have submitted this as the fist iteration from a longer list of
feature that I want to add to the driver, including events and maybe
interrupts.
If nobody has anything against, I would like to add a separate driver
for EMC18XX into the IIO.
Thanks and Best Regards,
Marius
next prev parent reply other threads:[~2025-09-25 9:09 UTC|newest]
Thread overview: 19+ 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
2025-09-25 9:09 ` Marius.Cristea [this message]
2025-09-25 14:32 ` Guenter Roeck
2025-09-27 15:04 ` Jonathan Cameron
-- strict thread matches above, loose matches on Subject: below --
2025-10-29 15:50 Marius Cristea
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=e6ab5becf5908d83857fcfd57823ffd259e6db90.camel@microchip.com \
--to=marius.cristea@microchip.com \
--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=linux@roeck-us.net \
--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;
as well as URLs for NNTP newsgroup(s).