Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jean-Baptiste Maneyrol via B4 Relay
	<devnull+jean-baptiste.maneyrol.tdk.com@kernel.org>
Cc: jean-baptiste.maneyrol@tdk.com,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Jean-Baptiste Maneyrol" <jmaneyrol@invensense.com>
Subject: Re: [PATCH v2 0/4] inv_icm42600 driver enhancements
Date: Mon, 31 Aug 2026 02:27:48 +0100	[thread overview]
Message-ID: <20260831022748.5b02e7b3@jic23-huawei> (raw)
In-Reply-To: <20260824-inv-icm42600-enhacements-v2-0-0040837fde12@tdk.com>

On Mon, 24 Aug 2026 14:30:06 +0200
Jean-Baptiste Maneyrol via B4 Relay <devnull+jean-baptiste.maneyrol.tdk.com@kernel.org> wrote:

> This series add enhancements patches to inv_icm42600 driver.
> 
> It includes:
> 1. Move of MEMS stabilization sleep before FIFO configuration to avoid
>    pushing incorrect data.
> 2. Use a fixed FIFO frame of 16 bits to avoid a bug of dynamic FIFO
>    configuration changed triggered by the sleep move.
> 3. Simplify watermark computation using gcd.
> 4. Enhance support of high frequency streaming by avoiding read of FIFO
>    count for watermark interrupt.
> 
> Signed-off-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Whilst sashiko did have quite a lot to say I 'think' they are all fine.
However, please do take a look and if you disagree then shout.

https://sashiko.dev/#/patchset/20260824-inv-icm42600-enhacements-v2-0-0040837fde12%40tdk.com

It may well be there are things in there that should be patches on top anyway.
I think all but 1 were things it even thought were preexisting issues.

Anyhow applied to the testing branch of iio.git which i just rebased
on rc1.

Thanks,

Jonathan


> ---
> Changes in v2:
> - Add commentaries for easing understanding of changes.
> - Reword commit messages with better explanations.
> - Link to v1: https://patch.msgid.link/20260820-inv-icm42600-enhacements-v1-0-075a881db557@tdk.com
> 
> To: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> To: Jonathan Cameron <jic23@kernel.org>
> To: David Lechner <dlechner@baylibre.com>
> To: Nuno Sá <nuno.sa@analog.com>
> To: Andy Shevchenko <andy@kernel.org>
> Cc: linux-iio@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org
> 
> ---
> Jean-Baptiste Maneyrol (4):
>       iio: imu: inv_icm42600: sleep before enabling FIFO data
>       iio: imu: inv_icm42600: use 2 sensors fixed packet size of 16 bytes
>       iio: imu: inv_icm42600: simplify watermark computation by using GCD
>       iio: imu: inv_icm42600: do not read FIFO count for watermark it
> 
>  drivers/iio/imu/inv_icm42600/inv_icm42600.h        |   4 +-
>  drivers/iio/imu/inv_icm42600/inv_icm42600_accel.c  |  16 ++-
>  drivers/iio/imu/inv_icm42600/inv_icm42600_buffer.c | 112 +++++++++------------
>  drivers/iio/imu/inv_icm42600/inv_icm42600_gyro.c   |  16 ++-
>  4 files changed, 73 insertions(+), 75 deletions(-)
> ---
> base-commit: 53c022f51fbe540fffee2121ce9ed3e15266c9a4
> change-id: 20260709-inv-icm42600-enhacements-1e0e18e6f868
> 
> Best regards,
> --  
> Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> 
> 


      parent reply	other threads:[~2026-08-31  1:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-24 12:30 [PATCH v2 0/4] inv_icm42600 driver enhancements Jean-Baptiste Maneyrol via B4 Relay
2026-08-24 12:30 ` [PATCH v2 1/4] iio: imu: inv_icm42600: sleep before enabling FIFO data Jean-Baptiste Maneyrol via B4 Relay
2026-08-24 12:30 ` [PATCH v2 2/4] iio: imu: inv_icm42600: use 2 sensors fixed packet size of 16 bytes Jean-Baptiste Maneyrol via B4 Relay
2026-08-24 12:30 ` [PATCH v2 3/4] iio: imu: inv_icm42600: simplify watermark computation by using GCD Jean-Baptiste Maneyrol via B4 Relay
2026-08-24 12:30 ` [PATCH v2 4/4] iio: imu: inv_icm42600: do not read FIFO count for watermark it Jean-Baptiste Maneyrol via B4 Relay
2026-08-31  1:27 ` 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=20260831022748.5b02e7b3@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=devnull+jean-baptiste.maneyrol.tdk.com@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jean-baptiste.maneyrol@tdk.com \
    --cc=jmaneyrol@invensense.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.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