From: Jonathan Cameron <jic23@kernel.org>
To: Remi Buisson via B4 Relay <devnull+remi.buisson.tdk.com@kernel.org>
Cc: remi.buisson@tdk.com, "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>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/9] dt-bindings: iio: imu: Add inv_icm45600
Date: Sat, 16 Aug 2025 12:25:19 +0100 [thread overview]
Message-ID: <20250816122519.2c7a5d9e@jic23-huawei> (raw)
In-Reply-To: <20250814-add_newport_driver-v4-1-4464b6600972@tdk.com>
On Thu, 14 Aug 2025 08:57:15 +0000
Remi Buisson via B4 Relay <devnull+remi.buisson.tdk.com@kernel.org> wrote:
> From: Remi Buisson <remi.buisson@tdk.com>
>
> Document the ICM-45600 devices devicetree bindings.
>
> Signed-off-by: Remi Buisson <remi.buisson@tdk.com>
> ---
> .../bindings/iio/imu/invensense,icm45600.yaml | 97 ++++++++++++++++++++++
> 1 file changed, 97 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/iio/imu/invensense,icm45600.yaml b/Documentation/devicetree/bindings/iio/imu/invensense,icm45600.yaml
> new file mode 100644
> index 0000000000000000000000000000000000000000..f43258124c32ebf850fc29b2e97643885e6f8480
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/iio/imu/invensense,icm45600.yaml
> @@ -0,0 +1,97 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/iio/imu/invensense,icm45600.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: InvenSense ICM-45600 Inertial Measurement Unit
> +
> +maintainers:
> + - Remi Buisson <remi.buisson@tdk.com>
> +
> +description: |
> + 6-axis MotionTracking device that combines a 3-axis gyroscope and a 3-axis
> + accelerometer.
> +
> + It has a configurable host interface that supports I3C, I2C and SPI serial
> + communication, features up to 8kB FIFO and 2 programmable interrupts with
> + ultra-low-power wake-on-motion support to minimize system power consumption.
> +
> + Other industry-leading features include InvenSense on-chip APEX Motion
> + Processing engine for gesture recognition, activity classification, and
> + pedometer, along with programmable digital filters, and an embedded
> + temperature sensor.
> +
> + https://invensense.tdk.com/wp-content/uploads/documentation/DS-000576_ICM-45605.pdf
> +
> +properties:
> + compatible:
> + enum:
> + - invensense,icm45605
> + - invensense,icm45606
> + - invensense,icm45608
> + - invensense,icm45634
> + - invensense,icm45686
> + - invensense,icm45687
> + - invensense,icm45688p
> + - invensense,icm45689
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + minItems: 1
> + maxItems: 2
> +
> + interrupt-names:
> + minItems: 1
> + maxItems: 2
> + items:
> + enum:
> + - INT1
> + - INT2
> + description: Choose chip interrupt pin to be used as interrupt input.
See v1 review on this from Krzysztof that you seem to have missed.
> +
> + drive-open-drain:
> + type: boolean
> +
> + vdd-supply:
Description doesn't add much so simply
vdd-supply: true
Might be enough.
> + description: Regulator that provides power to the sensor
> +
> + vddio-supply:
> + description: Regulator that provides power to the bus
Also very standard description so probably doesn't add anything.
> +
> + mount-matrix:
> + description: an optional 3x3 mounting rotation matrix
Could do
mount-matrix: true
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
Needed for any functionality to be available?
Note that this isn't a question of what driver currently requires, but
more what someone could implement if they happen not to have wired interrupts.
That happens annoyingly often!
Jonathan
> + - interrupt-names
> + - vdd-supply
> + - vddio-supply
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + #include <dt-bindings/gpio/gpio.h>
> + #include <dt-bindings/interrupt-controller/irq.h>
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + imu@68 {
> + compatible = "invensense,icm45605";
> + reg = <0x68>;
> + interrupt-parent = <&gpio2>;
> + interrupt-names = "INT1";
> + interrupts = <7 IRQ_TYPE_EDGE_RISING>;
> + vdd-supply = <&vdd>;
> + vddio-supply = <&vddio>;
> + mount-matrix = "0", "-1", "0",
> + "1", "0", "0",
> + "0", "0", "1";
> + };
> + };
>
next prev parent reply other threads:[~2025-08-16 11:25 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 8:57 [PATCH v4 0/9] iio: imu: new inv_icm45600 driver Remi Buisson via B4 Relay
2025-08-14 8:57 ` [PATCH v4 1/9] dt-bindings: iio: imu: Add inv_icm45600 Remi Buisson via B4 Relay
2025-08-15 8:46 ` Krzysztof Kozlowski
2025-08-18 8:35 ` Remi Buisson
2025-08-16 11:25 ` Jonathan Cameron [this message]
2025-08-19 12:54 ` Remi Buisson
2025-08-14 8:57 ` [PATCH v4 2/9] iio: imu: inv_icm45600: add new inv_icm45600 driver Remi Buisson via B4 Relay
2025-08-16 11:46 ` Jonathan Cameron
2025-08-19 12:56 ` Remi Buisson
2025-08-14 8:57 ` [PATCH v4 3/9] iio: imu: inv_icm45600: add buffer support in iio devices Remi Buisson via B4 Relay
2025-08-16 12:00 ` Jonathan Cameron
2025-08-19 12:58 ` Remi Buisson
2025-08-14 8:57 ` [PATCH v4 4/9] iio: imu: inv_icm45600: add IMU IIO gyroscope device Remi Buisson via B4 Relay
2025-08-16 12:08 ` Jonathan Cameron
2025-08-19 12:59 ` Remi Buisson
2025-08-14 8:57 ` [PATCH v4 5/9] iio: imu: inv_icm45600: add IMU IIO accelerometer device Remi Buisson via B4 Relay
2025-08-14 8:57 ` [PATCH v4 6/9] iio: imu: inv_icm45600: add I2C driver for inv_icm45600 driver Remi Buisson via B4 Relay
2025-08-15 11:31 ` kernel test robot
2025-08-16 12:16 ` Jonathan Cameron
2025-08-19 12:59 ` Remi Buisson
2025-08-14 8:57 ` [PATCH v4 7/9] iio: imu: inv_icm45600: add SPI " Remi Buisson via B4 Relay
2025-08-14 8:57 ` [PATCH v4 8/9] iio: imu: inv_icm45600: add I3C " Remi Buisson via B4 Relay
2025-08-14 8:57 ` [PATCH v4 9/9] MAINTAINERS: add entry for inv_icm45600 6-axis imu sensor Remi Buisson via B4 Relay
2025-08-16 12:17 ` Jonathan Cameron
2025-08-19 13:01 ` Remi Buisson
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=20250816122519.2c7a5d9e@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+remi.buisson.tdk.com@kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=remi.buisson@tdk.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