From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Bharadwaj Raju" <bharadwaj.raju777@gmail.com>,
"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>
Cc: linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, shuah@kernel.org,
linux-kernel-mentees@lists.linux.dev
Subject: Re: [PATCH 1/5] dt-bindings: iio: imu: Add ICM-20948
Date: Sun, 31 Aug 2025 14:57:38 +0200 [thread overview]
Message-ID: <f39bf664-1c06-4ef9-a8db-65b53b5e5270@kernel.org> (raw)
In-Reply-To: <20250831-icm20948-v1-1-1fe560a38de4@gmail.com>
On 30/08/2025 20:42, Bharadwaj Raju wrote:
> +description: |
> + 9-axis motion-tracking device that combines a 3-axis gyroscope, 3-axis
> + accelerometer, and a 3-axis magnetometer.
> +
> + https://invensense.tdk.com/wp-content/uploads/2024/03/DS-000189-ICM-20948-v1.6.pdf
> +
> +properties:
> + compatible:
> + enum:
> + - invensense,icm20948
> +
That's pretty incomplete. See existing invense bindings. Explain in
commit msg how this is different than existing devices.
> + reg:
> + maxItems: 1
> +
> +examples:
> + - |
> + i2c {
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + icm20948 {
Node names should be generic. See also an explanation and list of
examples (not exhaustive) in DT specification:
https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
If you cannot find a name matching your device, please check in kernel
sources for similar cases or you can grow the spec (via pull request to
DT spec repo).
> + compatible = "invensense,icm20948";
> + reg = <0x69>;
> + }
> + }
>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-08-31 12:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 18:42 [PATCH 0/5] iio: imu: New driver for InvenSense ICM-20948 9-Axis sensor Bharadwaj Raju
2025-08-30 18:42 ` [PATCH 1/5] dt-bindings: iio: imu: Add ICM-20948 Bharadwaj Raju
2025-08-31 12:57 ` Krzysztof Kozlowski [this message]
2025-09-01 3:29 ` Krzysztof Kozlowski
2025-08-30 18:42 ` [PATCH 2/5] iio: imu: add inv_icm20948 Bharadwaj Raju
2025-08-30 20:42 ` Andy Shevchenko
2025-09-01 19:19 ` Jonathan Cameron
2025-08-30 18:42 ` [PATCH 3/5] iio: imu: icm20948: add support for gyroscope Bharadwaj Raju
2025-08-31 12:58 ` Krzysztof Kozlowski
2025-08-31 23:09 ` kernel test robot
2025-09-01 1:36 ` kernel test robot
2025-09-01 19:31 ` Jonathan Cameron
2025-08-30 18:42 ` [PATCH 4/5] MAINTAINERS: add entry for inv_icm20948 driver Bharadwaj Raju
2025-09-01 19:32 ` Jonathan Cameron
2025-08-30 18:42 ` [PATCH 5/5] iio: imu: icm20948: add runtime power management support Bharadwaj Raju
2025-08-31 19:23 ` Markus Elfring
2025-09-01 6:08 ` Greg KH
2025-09-01 19:40 ` Jonathan Cameron
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=f39bf664-1c06-4ef9-a8db-65b53b5e5270@kernel.org \
--to=krzk@kernel.org \
--cc=andy@kernel.org \
--cc=bharadwaj.raju777@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).