linux-kernel - Re: [PATCH v2 0/8] iio: imu: new inv

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <k3pvwgafvocfqu2bntoz4heukfvpy34oycl3jdbc7hm2ewgfoo@mjyz4tszvt45>
Date: Tue, 15 Jul 2025 09:18:13 +0000
From: Sean Nyekjaer <sean@...nix.com>
To: Remi Buisson <Remi.Buisson@....com>
Cc: Jonathan Cameron <jic23@...nel.org>, David Lechner <dlechner@...libre.com>, Nuno Sá <nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>, Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v2 0/8] iio: imu: new inv_icm45600 driver

On Tue, Jul 15, 2025 at 09:03:57AM +0100, Remi Buisson wrote:
> >>This Message Is From an External Sender
> >>This message came from outside your organization.
> >>
> >>

[...]

> >>
> >> The structure of the driver is quite similar to the inv_icm42600 driver,
> >> however there are significant reasons for adding a different driver for
> >> inv_icm45600, such as:
> >> - A completely different register map.
> True, but icm45600 and icm42670 are more similar regarding indirect access
> and FIFO management.
> >At one point we asked TDK/Invense for a driver for icm42670. It also
> >have a completely different register map... Grrr :S
> >
> >Anyhow, should we combine these drivers in inv_icm42600? Like
> >st_lsm6dsx?
> I don't believe so for icm42600 and icm45600, because of the exposed reasons,
> they won't share much in the end.
> However, new parts like icm56600 might share the same driver than icm45600.
> (even with different memory maps :( )

Thanks for the clarification.

/Sean