From: Jonathan Cameron <jic23@kernel.org>
To: michael.srba@seznam.cz
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Jean-Baptiste Maneyrol <jmaneyrol@invensense.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 0/2] iio: imu: inv_mpu6050: Add support for ICM-20608-D
Date: Sun, 27 Mar 2022 16:05:39 +0100 [thread overview]
Message-ID: <20220327160530.41befccc@jic23-huawei> (raw)
In-Reply-To: <20220323121550.16096-1-michael.srba@seznam.cz>
On Wed, 23 Mar 2022 13:15:48 +0100
michael.srba@seznam.cz wrote:
> 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.
Series applied to my local togreg branch, but I'll be rebasing that after
rc1 so for now only pushed out as testing to let 0-day see if it can
find anything we missed.
Thanks,
Jonathan
>
> changelog:
> -v2: require specifying "invensense,icm20608" as a fallback compatible
> in the binding, as suggested
> -v3: fix indentation issue with the binding
>
> Michael Srba (2):
> dt-bindings: iio: imu: mpu6050: Document invensense,icm20608d
> iio: imu: inv_mpu6050: Add support for ICM-20608-D
>
> .../bindings/iio/imu/invensense,mpu6050.yaml | 34 +++++++++++--------
> 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, 43 insertions(+), 17 deletions(-)
>
next prev parent reply other threads:[~2022-03-27 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 12:15 [PATCH v2 0/2] iio: imu: inv_mpu6050: Add support for ICM-20608-D michael.srba
2022-03-23 12:15 ` [PATCH v3 1/2] dt-bindings: iio: imu: mpu6050: Document invensense,icm20608d michael.srba
2022-03-23 14:26 ` Krzysztof Kozlowski
2022-03-23 16:00 ` Rob Herring
2022-03-23 12:15 ` [PATCH v3 2/2] iio: imu: inv_mpu6050: Add support for ICM-20608-D michael.srba
2022-03-27 15:05 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-11 16:15 [PATCH v2 0/2] " michael.srba
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=20220327160530.41befccc@jic23-huawei \
--to=jic23@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jmaneyrol@invensense.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=michael.srba@seznam.cz \
--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).