All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Kanak Shilledar <kanak.shilledar@axis.com>
Cc: "Jonathan Cameron" <jic23@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <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>,
	"Henrik Grimler" <henrik.grimler@axis.com>,
	"Jean-Baptiste Maneyrol" <jean-baptiste.maneyrol@tdk.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@axis.com
Subject: Re: [PATCH v2 0/3] Add driver for Invensense ICM42370P accelerometer
Date: Mon, 17 Aug 2026 10:19:05 +0300	[thread overview]
Message-ID: <aoK16fva9ps8XNwb@ashevche-desk.local> (raw)
In-Reply-To: <20260813-b4-inv_icm42370p-v2-0-11aedfdf76d3@axis.com>

On Thu, Aug 13, 2026 at 02:26:09PM +0200, Kanak Shilledar wrote:
> Invensense ICM42370P is a high performance MEMS MotionTracking 3-axis
> accelerometer. It supports I2C, I3C and SPI protocols. It has a 2.25kB
> FIFO and two programmable interrupts with support for ultra-low-power
> wake-on-motion support. It has a built-in temperature sensor. This
> patch series adds basic support for the sensor with functionality of
> performing raw reads and writes along with buffered reads via the I2C
> interface.
> 
> This device contains 4 register banks for configuring the device called
> MREG0, MREG1, MREG2 and MREG3. Unlike other devices from the same
> vendor, this contains a very different way of accessing the register
> banks apart from the default user bank 0 (MREG0). The register bank access
> procedure is mentioned in the datasheet [1] Section 13. Due to this
> specific reason and that it doesn't have a gyro sensor, it is implemented
> as a standalone driver.
> 
> This device has 3 formats for the FIFO structure (datasheet [1] Section
> 6), currently only FIFO packet format 1 is supported, others
> formats can be added as part of future work.
> 
> The device supports EDGE and LEVEL triggered interrupts, refer the dt-binding
> for example of how the devicetree should be setup.
> 
> The driver is inspired from iio/imu/inv_icm42600.
> 
> Thanks to the reviewers for all the time you spent going through the
> code and the comments. The changes for v2 are quite a lot and I hope
> that every important change is documented in the changelog. After
> implementing the suggested changes, the driver is in a far better state
> than v1.

> [1] https://uat.invensense.com/en-us/products/3-axis/icm-42370-p

Can be added as a Datasheet tag here (and be spread by `b4` to all patches in
the series, which I think is fine).

Can you split the first patch to be based on the features implemented?
Something like

- patch 0: DT binding
- patch 1: very basic (but working) driver
- patch 2...n: Features 1...(n-1)

-- 
With Best Regards,
Andy Shevchenko



  parent reply	other threads:[~2026-08-17  7:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-13 12:26 [PATCH v2 0/3] Add driver for Invensense ICM42370P accelerometer Kanak Shilledar
2026-08-13 12:26 ` [PATCH v2 1/3] dt-bindings: Add InvenSense ICM-42370-p accelerometer Kanak Shilledar
2026-08-13 12:34   ` sashiko-bot
2026-08-18  7:51     ` Krzysztof Kozlowski
2026-08-18  7:56   ` Krzysztof Kozlowski
2026-08-13 12:26 ` [PATCH v2 2/3] iio: accel: Add support for ICM42370P Kanak Shilledar
2026-08-13 12:41   ` sashiko-bot
2026-08-16  2:59   ` Jonathan Cameron
2026-08-24  9:33     ` Kanak Shilledar
2026-08-13 12:26 ` [PATCH v2 3/3] iio: accel: icm42370: Add FIFO buffer functionality Kanak Shilledar
2026-08-13 12:40   ` sashiko-bot
2026-08-16  3:12   ` Jonathan Cameron
2026-08-17  9:48   ` Joshua Crofts
2026-08-17  7:19 ` Andy Shevchenko [this message]
2026-08-20 14:02   ` [PATCH v2 0/3] Add driver for Invensense ICM42370P accelerometer Kanak Shilledar
2026-08-20 15:19 ` Jean-Baptiste Maneyrol
2026-08-24  9:38   ` Kanak Shilledar

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=aoK16fva9ps8XNwb@ashevche-desk.local \
    --to=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=henrik.grimler@axis.com \
    --cc=jean-baptiste.maneyrol@tdk.com \
    --cc=jic23@kernel.org \
    --cc=kanak.shilledar@axis.com \
    --cc=kernel@axis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.