mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com>
Cc: "Jorijn van der Graaf" <jorijnvdgraaf@catcrafts.net>,
	"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>,
	"Chris Morgan" <macromorgan@hotmail.com>,
	"Luca Weiss" <luca.weiss@fairphone.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] iio: imu: inv_icm42600: add support for icm42630
Date: Fri, 24 Jul 2026 01:25:05 +0100	[thread overview]
Message-ID: <20260724012505.02029e51@jic23-huawei> (raw)
In-Reply-To: <BE1P281MB142628222E8A8A94CDBB5693CEC22@BE1P281MB1426.DEUP281.PROD.OUTLOOK.COM>

On Tue, 21 Jul 2026 07:18:02 +0000
Jean-Baptiste Maneyrol <Jean-Baptiste.Maneyrol@tdk.com> wrote:

> >
> >________________________________________
> >From: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>
> >Sent: Monday, July 20, 2026 19:34
> >To: Jonathan Cameron; Jean-Baptiste Maneyrol
> >Cc: Jorijn van der Graaf; David Lechner; Nuno Sá; Andy Shevchenko; Rob Herring; Krzysztof Kozlowski; Conor Dooley; Chris Morgan; Luca Weiss; linux-iio@vger.kernel.org; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org
> >Subject: [PATCH 2/2] iio: imu: inv_icm42600: add support for icm42630
> >
> >The TDK InvenSense ICM-42630 is a 6-axis IMU of the ICM-42600 family, found e. g. in the Fairphone 6. It is register-compatible with its siblings (the existing driver works on it unmodified) and reports WHOAMI value 0x0C. The part appears to
> >ZjQcmQRYFpfptBannerStart
> >This Message Is From an External Sender
> >This message came from outside your organization.
> >
> >ZjQcmQRYFpfptBannerEnd
> >
> >The TDK InvenSense ICM-42630 is a 6-axis IMU of the ICM-42600 family,
> >found e.g. in the Fairphone 6. It is register-compatible with its
> >siblings (the existing driver works on it unmodified) and reports
> >WHOAMI value 0x0C.
> >
> >The part appears to be a mobile SKU and has no public datasheet: the
> >identity comes from the Fairphone 6 platform documentation and
> >schematics naming the part, and the WHOAMI value was read from the
> >hardware, whose bank 0 register defaults match the ICM-42600 family
> >layout.
> >
> >Add the chip id, WHOAMI value and I2C/SPI match entries, using the
> >family default configuration like the ICM-42631.
> >
> >Tested on the Fairphone 6 via a backport of this change to the
> >device's 7.1-based kernel (only the id-table style adjusted to that
> >base), on a bit-banged SPI bus with INT1 wired to the SoC: probe,
> >accelerometer, gyroscope and temperature raw reads, all full-scale
> >ranges, multiple sampling frequencies, and watermark-paced FIFO reads
> >through the INT1 interrupt.
> >
> >Assisted-by: Claude:claude-fable-5
> >Signed-off-by: Jorijn van der Graaf <jorijnvdgraaf@catcrafts.net>

Just one minor thing inline

> >diff --git a/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c b/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> >index 28552d2db91d..c413904c8680 100644
> >--- a/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> >+++ b/drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c
> >@@ -81,6 +81,7 @@ static const struct i2c_device_id inv_icm42600_id[] = {
> >        { .name = "icm42622", .driver_data = INV_CHIP_ICM42622 },
> >        { .name = "icm42688", .driver_data = INV_CHIP_ICM42688 },
> >        { .name = "icm42631", .driver_data = INV_CHIP_ICM42631 },
> >+       { .name = "icm42630", .driver_data = INV_CHIP_ICM42630 },
> >        { }
> > };
> > MODULE_DEVICE_TABLE(i2c, inv_icm42600_id);
> >@@ -107,6 +108,9 @@ static const struct of_device_id inv_icm42600_of_matches[] = {
> >        }, {
> >                .compatible = "invensense,icm42631",
> >                .data = (void *)INV_CHIP_ICM42631,
> >+       }, {
> >+               .compatible = "invensense,icm42630",
> >+               .data = (void *)INV_CHIP_ICM42630,
> >        },
> >        { }
> > };
> >diff --git a/drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c b/drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c
> >index faf743bc6444..a1d12ce3bf87 100644
> >--- a/drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c
> >+++ b/drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c
> >@@ -78,6 +78,7 @@ static const struct spi_device_id inv_icm42600_id[] = {
> >        { .name = "icm42622", .driver_data = INV_CHIP_ICM42622 },
> >        { .name = "icm42688", .driver_data = INV_CHIP_ICM42688 },
> >        { .name = "icm42631", .driver_data = INV_CHIP_ICM42631 },
> >+       { .name = "icm42630", .driver_data = INV_CHIP_ICM42630 },
> >        { }
> > };
> > MODULE_DEVICE_TABLE(spi, inv_icm42600_id);
> >@@ -104,6 +105,9 @@ static const struct of_device_id inv_icm42600_of_matches[] = {
> >        }, {
> >                .compatible = "invensense,icm42631",
> >                .data = (void *)INV_CHIP_ICM42631,
> >+       }, {
> >+               .compatible = "invensense,icm42630",
> >+               .data = (void *)INV_CHIP_ICM42630,
> >        },

Hmm. These tables should ideally be in numeric order.   That can be
a separate follow up patch though.   For this one can you just
put it before the 42631 here and wherever else that is relevant.

If you don't mind doing a precursor patch to reorder the entrees
then even better!

Thanks,

Jonathan

> >        { }
> > };
> >--
> >2.55.0
> >  
> 
> Hello Jorijn,
> 
> it is OK for me, thanks for the patch.
> 
> Acked-by: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
> 
> Thanks,
> JB

  reply	other threads:[~2026-07-24  0:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-20 17:34 [PATCH 0/2] " Jorijn van der Graaf
2026-07-20 17:34 ` [PATCH 1/2] dt-bindings: iio: imu: icm42600: add icm42630 Jorijn van der Graaf
2026-07-21  7:14   ` Jean-Baptiste Maneyrol
2026-07-21 16:01   ` Conor Dooley
2026-07-21 17:16     ` Jorijn van der Graaf
2026-07-22 16:59       ` Conor Dooley
2026-07-24  0:22         ` Jonathan Cameron
2026-07-20 17:34 ` [PATCH 2/2] iio: imu: inv_icm42600: add support for icm42630 Jorijn van der Graaf
2026-07-21  7:18   ` Jean-Baptiste Maneyrol
2026-07-24  0:25     ` Jonathan Cameron [this message]
2026-07-21  7:12 ` [PATCH 0/2] " Jean-Baptiste Maneyrol

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=20260724012505.02029e51@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Jean-Baptiste.Maneyrol@tdk.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jorijnvdgraaf@catcrafts.net \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.weiss@fairphone.com \
    --cc=macromorgan@hotmail.com \
    --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

all inboxes | Powered by JetHome®