mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hermes Zhang <chenhuiz@axis.com>
To: <jic23@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
	<robh+dt@kernel.org>,
	Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
Cc: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kernel@axis.com>, Hermes Zhang <chenhuiz@axis.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	<devicetree@vger.kernel.org>
Subject: [PATCH 2/2] dt-bindings: iio: imu: mpu6050: Add icm20600 bindings to mpu6050
Date: Fri, 21 Apr 2023 15:16:30 +0800	[thread overview]
Message-ID: <20230421071630.524822-3-chenhuiz@axis.com> (raw)
In-Reply-To: <20230421071630.524822-1-chenhuiz@axis.com>

Adding the invensense ICM-20600 to the compatible list of the mpu6050
driver

Signed-off-by: Hermes Zhang <chenhuiz@axis.com>
---
 .../devicetree/bindings/iio/imu/invensense,mpu6050.yaml          | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
index ec64d7877fe5..67711bc0ee6c 100644
--- a/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
+++ b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
@@ -20,6 +20,7 @@ properties:
           - invensense,icm20608
           - invensense,icm20609
           - invensense,icm20689
+          - invensense,icm20600
           - invensense,icm20602
           - invensense,icm20690
           - invensense,mpu6000
-- 
2.30.2


  parent reply	other threads:[~2023-04-21  7:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21  7:16 [PATCH 0/2] Add support for the ICM 20600 IMU Hermes Zhang
2023-04-21  7:16 ` [PATCH 1/2] iio: imu: mpu6050: " Hermes Zhang
2023-04-22 17:21   ` Jonathan Cameron
2023-04-21  7:16 ` Hermes Zhang [this message]
2023-04-21  8:23   ` [PATCH 2/2] dt-bindings: iio: imu: mpu6050: Add icm20600 bindings to mpu6050 Krzysztof Kozlowski
2023-04-22  6:14     ` Hermes Zhang
2023-04-22 17:19       ` 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=20230421071630.524822-3-chenhuiz@axis.com \
    --to=chenhuiz@axis.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@kernel.org \
    --cc=jmaneyrol@invensense.com \
    --cc=kernel@axis.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@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®