From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: michael.srba@seznam.cz, 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
Subject: Re: [PATCH v2 1/2] dt-bindings: iio: imu: mpu6050: Document invensense,icm20608d
Date: Fri, 11 Mar 2022 18:15:06 +0100 [thread overview]
Message-ID: <e9f0024a-461f-9f64-aa19-94b5ccf35be3@canonical.com> (raw)
In-Reply-To: <20220311161600.1469-2-michael.srba@seznam.cz>
On 11/03/2022 17:15, michael.srba@seznam.cz wrote:
> From: Michael Srba <Michael.Srba@seznam.cz>
>
> ICM-20608-D differs from the other ICM-20608 variants by having
> a DMP (Digital Motion Processor) core tacked on.
> Despite having a different WHOAMI register, this variant is
> completely interchangeable with the other ICM-20608 variants
> by simply pretending the DMP core doesn't exist.
>
> Signed-off-by: Michael Srba <Michael.Srba@seznam.cz>
> ---
> changelog:
> - v2: require specifying "invensense,icm20608" as a fallback compatible
> ---
> .../bindings/iio/imu/invensense,mpu6050.yaml | 34 +++++++++++--------
> 1 file changed, 19 insertions(+), 15 deletions(-)
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-03-11 17:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 16:15 [PATCH v2 0/2] iio: imu: inv_mpu6050: Add support for ICM-20608-D michael.srba
2022-03-11 16:15 ` [PATCH v2 1/2] dt-bindings: iio: imu: mpu6050: Document invensense,icm20608d michael.srba
2022-03-11 17:15 ` Krzysztof Kozlowski [this message]
2022-03-12 3:41 ` Rob Herring
2022-03-20 15:15 ` Jonathan Cameron
2022-03-20 17:56 ` Rob Herring
2022-03-21 14:58 ` Jonathan Cameron
2022-03-11 16:16 ` [PATCH v2 2/2] iio: imu: inv_mpu6050: Add support for ICM-20608-D michael.srba
2022-03-11 17:16 ` Krzysztof Kozlowski
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=e9f0024a-461f-9f64-aa19-94b5ccf35be3@canonical.com \
--to=krzysztof.kozlowski@canonical.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jmaneyrol@invensense.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).