From: Stephan Gerhold <stephan@gerhold.net>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Rob Herring <robh+dt@kernel.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>,
Stephan Gerhold <stephan@gerhold.net>
Subject: [PATCH 1/2] dt-bindings: iio: imu: mpu6050: Document invensense,mpu6880
Date: Wed, 2 Dec 2020 11:13:54 +0100 [thread overview]
Message-ID: <20201202101355.87112-1-stephan@gerhold.net> (raw)
MPU-6880 seems to be very similar to MPU-6500 / MPU-6050 and it works
fine with some minor additions for the mpu6050 driver.
Add a compatible for it to the binding documentation.
Cc: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>
Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
---
Note: This applies only on top of the patch for the YAML conversion:
https://lore.kernel.org/linux-iio/20201128173343.390165-3-jic23@kernel.org/
I guess that one will be applied very soon so I think this is easier :)
---
.../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 9268b6ca2afe..edbc2921aabd 100644
--- a/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
+++ b/Documentation/devicetree/bindings/iio/imu/invensense,mpu6050.yaml
@@ -25,6 +25,7 @@ properties:
- invensense,mpu6050
- invensense,mpu6500
- invensense,mpu6515
+ - invensense,mpu6880
- invensense,mpu9150
- invensense,mpu9250
- invensense,mpu9255
--
2.29.2
next reply other threads:[~2020-12-02 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 10:13 Stephan Gerhold [this message]
2020-12-02 10:13 ` [PATCH 2/2] iio: imu: inv_mpu6050: Add support for MPU-6880 Stephan Gerhold
2020-12-02 10:28 ` Jean-Baptiste Maneyrol
2020-12-02 10:43 ` Stephan Gerhold
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=20201202101355.87112-1-stephan@gerhold.net \
--to=stephan@gerhold.net \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jmaneyrol@invensense.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--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;
as well as URLs for NNTP newsgroup(s).