linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: <victor.duicu@microchip.com>
Cc: <andy@kernel.org>, <dlechner@baylibre.com>, <nuno.sa@analog.com>,
	<marius.cristea@microchip.com>, <linux-iio@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] add support for MCP998X
Date: Tue, 15 Apr 2025 18:43:08 +0100	[thread overview]
Message-ID: <20250415184308.2deb6d3f@jic23-huawei> (raw)
In-Reply-To: <20250415132623.14913-1-victor.duicu@microchip.com>

On Tue, 15 Apr 2025 16:26:21 +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 chip is capable of monitoring temperatures on four
> external channels and one internal.
Hi Victor,

This gets the standard question for a temperature sensor...
Why IIO and not hwmon?  Good to have that info in the cover letter or
patch description.

I'd normally moan about the wild cards even though they are only
in patch titles, but meh, the datasheet uses the wild card
so we are probably safe for a while at least!

Jonathan


> 
> Victor Duicu (2):
>   dt-bindings: iio: temperature: add support for MCP998X
>   iio: temperature: add support for MCP998X
> 
>  .../testing/sysfs-bus-iio-temperature-mcp9982 |  17 +
>  .../iio/temperature/microchip,mcp9982.yaml    | 182 ++++
>  MAINTAINERS                                   |   7 +
>  drivers/iio/temperature/Kconfig               |  10 +
>  drivers/iio/temperature/Makefile              |   1 +
>  drivers/iio/temperature/mcp9982.c             | 794 ++++++++++++++++++
>  6 files changed, 1011 insertions(+)
>  create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-temperature-mcp9982
>  create mode 100644 Documentation/devicetree/bindings/iio/temperature/microchip,mcp9982.yaml
>  create mode 100644 drivers/iio/temperature/mcp9982.c
> 
> 
> base-commit: 31c52fe3b2efeebfc72cc5336653baaa9889b41e


  parent reply	other threads:[~2025-04-15 17:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 13:26 [PATCH v1 0/2] add support for MCP998X victor.duicu
2025-04-15 13:26 ` [PATCH v1 1/2] dt-bindings: iio: temperature: " victor.duicu
2025-04-15 17:52   ` Jonathan Cameron
2025-04-17 11:40     ` Victor.Duicu
2025-04-18 16:01       ` Jonathan Cameron
2025-04-16  6:45   ` Krzysztof Kozlowski
2025-04-15 13:26 ` [PATCH v1 2/2] " victor.duicu
2025-04-15 19:05   ` Andy Shevchenko
2025-05-22  9:18     ` Victor.Duicu
2025-05-23 16:21       ` Andy Shevchenko
2025-04-18 18:07   ` Jonathan Cameron
2025-04-28 12:57     ` Victor.Duicu
2025-04-30 16:17       ` Jonathan Cameron
2025-04-15 17:43 ` Jonathan Cameron [this message]
2025-04-17  7:30   ` [PATCH v1 0/2] " Victor.Duicu

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=20250415184308.2deb6d3f@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marius.cristea@microchip.com \
    --cc=nuno.sa@analog.com \
    --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).