From: Krzysztof Kozlowski <krzk@kernel.org>
To: victor.duicu@microchip.com
Cc: linux@roeck-us.net, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, corbet@lwn.net,
marius.cristea@microchip.com, linux-hwmon@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v1 0/2] add support in hwmon for MCP998X
Date: Sun, 2 Nov 2025 16:57:28 +0100 [thread overview]
Message-ID: <20251102-calm-fractal-labrador-cde4f0@kuoka> (raw)
In-Reply-To: <20251031155831.42763-1-victor.duicu@microchip.com>
On Fri, Oct 31, 2025 at 05:58:29PM +0200, victor.duicu@microchip.com wrote:
> From: Victor Duicu <victor.duicu@microchip.com>
>
> Add support in hwmon 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.
>
> The driver was tested on MCP9984 and MCP9985.
> The driver supports reading temperature channels and setting
> the update interval.
>
> Differences related to previous patch:
> v1:
> - initial version for review.
Huh? That's v1. What are you comparing?
> This is a continuation of the IIO driver:
> https://lore.kernel.org/all/20250930133131.13797-1-victor.duicu@microchip.com/
So v7?
Best regards,
Krzysztof
prev parent reply other threads:[~2025-11-02 15:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 15:58 [PATCH v1 0/2] add support in hwmon for MCP998X victor.duicu
2025-10-31 15:58 ` [PATCH v1 1/2] dt-bindings: hwmon: add support " victor.duicu
2025-10-31 15:58 ` [PATCH v1 2/2] " victor.duicu
2025-10-31 16:41 ` Guenter Roeck
2025-11-02 15:57 ` Krzysztof Kozlowski [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=20251102-calm-fractal-labrador-cde4f0@kuoka \
--to=krzk@kernel.org \
--cc=conor+dt@kernel.org \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=marius.cristea@microchip.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).