public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Marcus Folkesson <marcus.folkesson@gmail.com>
Cc: Kent Gustavsson <kent@minoris.se>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Cameron <Jonathan.Cameron@huawei.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	Kent Gustavsson <nedo80@gmail.com>,
	devicetree@vger.kernel.org,
	Lukas Rauber <lukas.rauber@janitza.de>
Subject: Re: [PATCH v2 0/3] MCP3911 fixes
Date: Mon, 5 May 2025 13:57:21 +0100	[thread overview]
Message-ID: <20250505135721.1ef655d7@jic23-huawei> (raw)
In-Reply-To: <20250428-mcp3911-fixes-v2-0-406e39330c3d@gmail.com>

On Mon, 28 Apr 2025 08:54:10 +0200
Marcus Folkesson <marcus.folkesson@gmail.com> wrote:

> This series contain two fixes for the MCP3911 driver:
> - Add support for reset signal
> - Fix wrong mapping for the coversion result registers
> 
> The register map for the conversion result registers of the MCP3911
> differs from the other variants so make sure we read from the right
> register by introducing device-dependent .read_raw() callbacks.
Applied to the togreg branch of iio.git and initially pushed out as testing
for 0-day to take a look.

Thanks,

Jonathan

> 
> Signed-off-by: Marcus Folkesson <marcus.folkesson@gmail.com>
> ---
> Changes in v2:
> - Fix review comments from Andy Shevchenko (Thanks Andy!)
> - Link to v1: https://lore.kernel.org/r/20250423-mcp3911-fixes-v1-0-5bd0b68ec481@gmail.com
> 
> ---
> Marcus Folkesson (3):
>       iio: adc: mcp3911: fix device dependent mappings for conversion result registers
>       dt-bindings: iio: adc: mcp3911: add reset-gpios
>       iio: adc: mcp3911: add reset management
> 
>  .../bindings/iio/adc/microchip,mcp3911.yaml        |  5 ++
>  drivers/iio/adc/mcp3911.c                          | 58 ++++++++++++++++++++--
>  2 files changed, 58 insertions(+), 5 deletions(-)
> ---
> base-commit: 1e26c5e28ca5821a824e90dd359556f5e9e7b89f
> change-id: 20250423-mcp3911-fixes-ef3b2145577d
> 
> Best regards,


      parent reply	other threads:[~2025-05-05 12:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-28  6:54 [PATCH v2 0/3] MCP3911 fixes Marcus Folkesson
2025-04-28  6:54 ` [PATCH v2 1/3] iio: adc: mcp3911: fix device dependent mappings for conversion result registers Marcus Folkesson
2025-04-28  7:45   ` Andy Shevchenko
2025-04-28  6:54 ` [PATCH v2 2/3] dt-bindings: iio: adc: mcp3911: add reset-gpios Marcus Folkesson
2025-04-28 16:40   ` Conor Dooley
2025-05-05 12:56     ` Jonathan Cameron
2025-04-28  6:54 ` [PATCH v2 3/3] iio: adc: mcp3911: add reset management Marcus Folkesson
2025-04-28  7:46   ` Andy Shevchenko
2025-05-05 12:57 ` 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=20250505135721.1ef655d7@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kent@minoris.se \
    --cc=krzk+dt@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukas.rauber@janitza.de \
    --cc=marcus.folkesson@gmail.com \
    --cc=nedo80@gmail.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