[PATCH v5 0/5] iio: mcp9600: Features and improvements

Ben Collins posted 5 patches 1 month, 2 weeks ago
There is a newer version of this series
.../iio/temperature/microchip,mcp9600.yaml    |  61 +++-
drivers/iio/temperature/Kconfig               |   8 +-
drivers/iio/temperature/mcp9600.c             | 295 +++++++++++++++++-
3 files changed, 341 insertions(+), 23 deletions(-)
[PATCH v5 0/5] iio: mcp9600: Features and improvements
Posted by Ben Collins 1 month, 2 weeks ago
From: Ben Collins <bcollins@watter.com>

ChangeLog:
v5 -> v6:
  - Fix accidental typo added in dt-bindings: IRQ_TYPE_EDGE_RISIN
  - Correct some constraints in dt-bindings
  - Reverse if/then for mcp9601 vs mcp9600 constraints in dt-bindings
  - Updates to changelog for patch 2/6 (dt-bindings mcp9600)
  - Cleanup tabs that were converted to spaces
  - Split thermocouple-type default to separate patch

v4 -> v5:
  - Missed a one line fix to IIR patch (5/5)

v3 -> v4:
  - Based on feedback from David Lechner <dlechner@baylibre.com>
    * Allow fallback compatible in dt-bindings for mcp9601.
  - Based on feedback from Jonathan Cameron <jic23@kernel.org>
    * Be explicit in patch description for fixed width changes.
    * Check chip_info for NULL to quiet warnings from kernel-test-robot
    * Remove "and similar" for long description of MCP9600.
  - Based on lots of feedback, use frequency values for IIR, and use
    filter_type[none, ema] to enable or disable.
  - Set default 3 for thermocouple in dt-binding
  - Rework open/short circuit in dt-bindings

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 (6):
  dt-bindings: iio: mcp9600: Set default 3 for thermocouple-type
  dt-bindings: iio: mcp9600: Add microchip,mcp9601 and add constraints
  iio: mcp9600: White space and fixed width cleanup
  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    |  61 +++-
 drivers/iio/temperature/Kconfig               |   8 +-
 drivers/iio/temperature/mcp9600.c             | 295 +++++++++++++++++-
 3 files changed, 341 insertions(+), 23 deletions(-)

-- 
2.39.5
Re: [PATCH v5 0/5] iio: mcp9600: Features and improvements
Posted by Krzysztof Kozlowski 1 month, 2 weeks ago
On Mon, Aug 18, 2025 at 02:32:08PM -0400, Ben Collins wrote:
> From: Ben Collins <bcollins@watter.com>
> 
> ChangeLog:
> v5 -> v6:
>   - Fix accidental typo added in dt-bindings: IRQ_TYPE_EDGE_RISIN
>   - Correct some constraints in dt-bindings
>   - Reverse if/then for mcp9601 vs mcp9600 constraints in dt-bindings
>   - Updates to changelog for patch 2/6 (dt-bindings mcp9600)
>   - Cleanup tabs that were converted to spaces
>   - Split thermocouple-type default to separate patch

Please start using b4, so you will get changelogs with lore links for
free and ALL your patches will be properly versioned. git can do that
as well - git format-patch -v5 --cover-letter, if you don't want to use
b4.

Best regards,
Krzysztof
Re: [PATCH v5 0/5] iio: mcp9600: Features and improvements
Posted by Jonathan Cameron 1 month, 2 weeks ago
On Tue, 19 Aug 2025 08:55:44 +0200
Krzysztof Kozlowski <krzk@kernel.org> wrote:

> On Mon, Aug 18, 2025 at 02:32:08PM -0400, Ben Collins wrote:
> > From: Ben Collins <bcollins@watter.com>
> > 
> > ChangeLog:
> > v5 -> v6:
> >   - Fix accidental typo added in dt-bindings: IRQ_TYPE_EDGE_RISIN
> >   - Correct some constraints in dt-bindings
> >   - Reverse if/then for mcp9601 vs mcp9600 constraints in dt-bindings
> >   - Updates to changelog for patch 2/6 (dt-bindings mcp9600)
> >   - Cleanup tabs that were converted to spaces
> >   - Split thermocouple-type default to separate patch  
> 
> Please start using b4, so you will get changelogs with lore links for
> free and ALL your patches will be properly versioned. git can do that
> as well - git format-patch -v5 --cover-letter, if you don't want to use
> b4.

Second that.  This is what it looks like in patchwork that I use
for managing reviews / merges etc.
https://patchwork.kernel.org/project/linux-iio/list/?series=992678

version number not easy to find as it gets dropped from the series title
and is only normally listed for the patches. 

> 
> Best regards,
> Krzysztof
>
Re: [PATCH v5 0/5] iio: mcp9600: Features and improvements
Posted by Ben Collins 1 month, 2 weeks ago
On Tue, Aug 19, 2025 at 07:24:55PM -0500, Jonathan Cameron wrote:
> On Tue, 19 Aug 2025 08:55:44 +0200
> Krzysztof Kozlowski <krzk@kernel.org> wrote:
> 
> > On Mon, Aug 18, 2025 at 02:32:08PM -0400, Ben Collins wrote:
> > > From: Ben Collins <bcollins@watter.com>
> > > 
> > > ChangeLog:
> > > v5 -> v6:
> > >   - Fix accidental typo added in dt-bindings: IRQ_TYPE_EDGE_RISIN
> > >   - Correct some constraints in dt-bindings
> > >   - Reverse if/then for mcp9601 vs mcp9600 constraints in dt-bindings
> > >   - Updates to changelog for patch 2/6 (dt-bindings mcp9600)
> > >   - Cleanup tabs that were converted to spaces
> > >   - Split thermocouple-type default to separate patch  
> > 
> > Please start using b4, so you will get changelogs with lore links for
> > free and ALL your patches will be properly versioned. git can do that
> > as well - git format-patch -v5 --cover-letter, if you don't want to use
> > b4.
> 
> Second that.  This is what it looks like in patchwork that I use
> for managing reviews / merges etc.
> https://patchwork.kernel.org/project/linux-iio/list/?series=992678
> 
> version number not easy to find as it gets dropped from the series title
> and is only normally listed for the patches. 

I appreciate both of you suggesting this. I've switched to b4 now and
now I don't know how anyone could not use it.

-- 
 Ben Collins
 https://libjwt.io
 https://github.com/benmcollins
 --
 3EC9 7598 1672 961A 1139  173A 5D5A 57C7 242B 22CF