From: michael.srba@seznam.cz
To: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>
Cc: Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Michael Srba <Michael.Srba@seznam.cz>
Subject: [PATCH 0/2] iio: imu: inv_mpu6050: Add support for ICM-20608-D
Date: Thu, 10 Mar 2022 14:39:36 +0100 [thread overview]
Message-ID: <20220310133938.2495-1-michael.srba@seznam.cz> (raw)
From: Michael Srba <Michael.Srba@seznam.cz>
This series copies the invensense icm20608 support in the inv_mpu6050
driver for icm20608d, which is for all intents and purposes identical,
except for the inclusion of a DMP (Digital Motion Processor), which
is deemed significant enough to change the WHOAMI value, thereby making
the driver fail if the invensense,icm20608 compatible is specified.
Since the driver doesn't currently acknowledge that there is such thing
as a DMP core, all that is needed is to copy the icm20608 support and
change the WHOAMI value.
Michael Srba (2):
dt-bindings: iio: imu: mpu6050: Document invensense,icm20608d
iio: imu: inv_mpu6050: Add support for ICM-20608-D
.../devicetree/bindings/iio/imu/invensense,mpu6050.yaml | 1 +
drivers/iio/imu/inv_mpu6050/Kconfig | 4 ++--
drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 9 +++++++++
drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c | 6 ++++++
drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 2 ++
drivers/iio/imu/inv_mpu6050/inv_mpu_spi.c | 5 +++++
6 files changed, 25 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2022-03-10 13:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 13:39 michael.srba [this message]
2022-03-10 13:39 ` [PATCH 1/2] dt-bindings: iio: imu: mpu6050: Document invensense,icm20608d michael.srba
2022-03-10 16:34 ` Krzysztof Kozlowski
2022-03-10 18:56 ` Michael Srba
2022-03-10 21:24 ` Krzysztof Kozlowski
2022-03-20 15:12 ` Jonathan Cameron
2022-03-21 8:04 ` Krzysztof Kozlowski
2022-03-21 15:04 ` Jonathan Cameron
2022-03-21 15:22 ` Krzysztof Kozlowski
2022-03-21 17:42 ` Jonathan Cameron
2022-03-21 18:07 ` Michael Srba
2022-03-22 10:19 ` Jonathan Cameron
2022-03-22 10:41 ` Krzysztof Kozlowski
2022-03-22 20:22 ` Jonathan Cameron
2022-03-22 10:23 ` Krzysztof Kozlowski
2022-03-22 20:29 ` Jonathan Cameron
2022-03-10 13:39 ` [PATCH 2/2] iio: imu: inv_mpu6050: Add support for ICM-20608-D michael.srba
2022-03-10 13:58 ` Jean-Baptiste Maneyrol
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=20220310133938.2495-1-michael.srba@seznam.cz \
--to=michael.srba@seznam.cz \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jmaneyrol@invensense.com \
--cc=lars@metafoo.de \
--cc=linux-iio@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;
as well as URLs for NNTP newsgroup(s).