From: Jonathan Cameron <jic23@kernel.org>
To: <victor.duicu@microchip.com>
Cc: <dlechner@baylibre.com>, <nuno.sa@analog.com>, <andy@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <marius.cristea@microchip.com>
Subject: Re: [PATCH v5 0/2] add support for MCP998X
Date: Sat, 20 Sep 2025 12:42:44 +0100 [thread overview]
Message-ID: <20250920124244.1c263df0@jic23-huawei> (raw)
In-Reply-To: <20250918111937.5150-1-victor.duicu@microchip.com>
On Thu, 18 Sep 2025 14:19:35 +0300
<victor.duicu@microchip.com> wrote:
> From: Victor Duicu <victor.duicu@microchip.com>
>
> Add support for Microchip MCP998X/33 and MCP998XD/33D Multichannel Automotive Temperature Monitor Family.
>
> The chips in the family have different numbers of external channels, ranging from 1 (MCP9982) to 4 channels (MCP9985).
> Reading diodes in anti-parallel connection is supported by MCP9984/85/33 and MCP9984D/85D/33D.
> Dedicated hardware shutdown circuitry is present only in MCP998XD and MCP9933D.
>
> Current version of driver does not support interrupts, events and data buffering.
Similar to the emc1812, this probably wants a short statement of why IIO rather than hwmon.
Given it is called out as an automotive sensor I'm more confident this one is suitable
for IIO, but still good to state that in the cover letter.
prev parent reply other threads:[~2025-09-20 11:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 11:19 [PATCH v5 0/2] add support for MCP998X victor.duicu
2025-09-18 11:19 ` [PATCH v5 1/2] dt-bindings: iio: temperature: " victor.duicu
2025-09-18 14:56 ` Conor Dooley
2025-09-18 11:19 ` [PATCH v5 2/2] " victor.duicu
2025-09-19 6:27 ` kernel test robot
2025-09-20 10:39 ` Jonathan Cameron
2025-09-19 6:59 ` kernel test robot
2025-09-20 10:55 ` Jonathan Cameron
2025-09-24 12:47 ` Victor.Duicu
2025-09-27 15:25 ` Jonathan Cameron
2025-09-20 11:42 ` Jonathan Cameron [this message]
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=20250920124244.1c263df0@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@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 \
--cc=victor.duicu@microchip.com \
/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).