From: Jonathan Cameron <jic23@kernel.org>
To: Ben Collins <bcollins@watter.com>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Ben Collins <bcollins@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Nuno Sa <nuno.sa@analog.com>, Andy Shevchenko <andy@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Andrew Hepp <andrew.hepp@ahepp.dev>
Subject: Re: [PATCH 0/5] iio: mcp9600: Features and improvements
Date: Sat, 16 Aug 2025 11:07:47 +0100 [thread overview]
Message-ID: <20250816110747.42696c91@jic23-huawei> (raw)
In-Reply-To: <20250815164627.22002-1-bcollins@watter.com>
On Fri, 15 Aug 2025 16:46:02 +0000
Ben Collins <bcollins@watter.com> wrote:
> From: Ben Collins <bcollins@kernel.org>
See submitting patches documentation. Should have a version number in the [] in the patch title.
Jonathan
>
> ChangeLog:
> v2 -> v3:
> - Improve changelogs in each patch
> - Based on feedback from Andy Shevchenko <andy.shevchenko@gmail.com>
> * Set register offsets to fixed width
> * Fix typos
> * Future-proof Kconfig changes
> * Convert to using chip_info paradigm
> * Verbiage: dt -> firmware description
> * Use proper specifiers and drop castings
> * Fix register offset to be fixed-width
> * u8 for cfg var
> * Fix % type for u32 to be %u
> * Make blank lines consistent between case statements
> * FIELD_PREP -> FIELD_MODIFY
> * Remove explicit setting of 0 value in filter_level
> - Based on feedback from David Lechner <dlechner@baylibre.com>
> * Rework IIR values exposed to sysfs. Using the ratios, there was no
> way to represent "disabled" (i.e. infinity). Based on the bmp280
> driver I went with using the power coefficients (e.g. 1, 2, 4, 8,
> ...) where 1 is disabled (n=0).
>
> v1 -> v2:
> - Break into individual patches
>
> v1:
> - Initial patch to enable IIR and thermocouple-type
> - Recognize mcp9601
>
> Ben Collins (5):
> dt-bindings: iio: mcp9600: Add compatible for microchip,mcp9601
> iio: mcp9600: White space cleanup for tab alignment
> iio: mcp9600: Recognize chip id for mcp9601
> iio: mcp9600: Add support for thermocouple-type
> iio: mcp9600: Add support for IIR filter
>
> .../iio/temperature/microchip,mcp9600.yaml | 6 +-
> drivers/iio/temperature/Kconfig | 8 +-
> drivers/iio/temperature/mcp9600.c | 209 ++++++++++++++++--
> 3 files changed, 201 insertions(+), 22 deletions(-)
>
prev parent reply other threads:[~2025-08-16 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 16:46 [PATCH 0/5] iio: mcp9600: Features and improvements Ben Collins
2025-08-15 16:46 ` [PATCH 1/5] dt-bindings: iio: mcp9600: Add compatible for microchip,mcp9601 Ben Collins
2025-08-16 9:58 ` Jonathan Cameron
2025-08-16 18:55 ` David Lechner
2025-08-17 16:37 ` Ben Collins
2025-08-17 16:51 ` David Lechner
2025-08-17 17:34 ` Ben Collins
2025-08-17 17:59 ` David Lechner
2025-08-17 21:02 ` Ben Collins
2025-08-17 21:10 ` Ben Collins
2025-08-18 6:42 ` Krzysztof Kozlowski
2025-08-16 10:07 ` 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=20250816110747.42696c91@jic23-huawei \
--to=jic23@kernel.org \
--cc=andrew.hepp@ahepp.dev \
--cc=andy@kernel.org \
--cc=bcollins@kernel.org \
--cc=bcollins@watter.com \
--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=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