From: Jay Greco <grecojay@amazon.com>
To: <linux-iio@vger.kernel.org>
Cc: <jorcrous@amazon.com>, Jay Greco <grecojay@amazon.com>,
"Jean-Baptiste Maneyrol" <jmaneyrol@invensense.com>,
Jonathan Cameron <jic23@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH v2 0/2] iio: imu: inv_icm42600: Add support for icm42631
Date: Thu, 10 Nov 2022 19:29:31 +0000 [thread overview]
Message-ID: <20221110192933.13616-1-grecojay@amazon.com> (raw)
This patch adds support for the invensense icm42631 as part of the
inv_icm42600 family driver within the IIO subsystem. The patch series
also includes the requisite changes to the dt-bindings documentation.
Changes in v2:
- Fix documentation subject prefix per Krzysztof Kozlowski
Changes in v1:
- initial patch submission
Jay Greco (2):
iio: imu: inv_icm42600: Add support for icm42631
dt-bindings: iio: imu: Add inv_icm42600 documentation
.../devicetree/bindings/iio/imu/invensense,icm42600.yaml | 1 +
drivers/iio/imu/inv_icm42600/inv_icm42600.h | 2 ++
drivers/iio/imu/inv_icm42600/inv_icm42600_core.c | 5 +++++
drivers/iio/imu/inv_icm42600/inv_icm42600_i2c.c | 3 +++
drivers/iio/imu/inv_icm42600/inv_icm42600_spi.c | 3 +++
5 files changed, 14 insertions(+)
--
2.37.1
next reply other threads:[~2022-11-10 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 19:29 Jay Greco [this message]
2022-11-10 19:29 ` [PATCH v2 1/2] iio: imu: inv_icm42600: Add support for icm42631 Jay Greco
2022-11-10 19:47 ` Jean-Baptiste Maneyrol
2022-11-10 19:29 ` [PATCH v2 2/2] dt-bindings: iio: imu: Add inv_icm42600 documentation Jay Greco
2022-11-10 19:48 ` Jean-Baptiste Maneyrol
2022-11-11 14:58 ` Krzysztof Kozlowski
2022-11-12 17:44 ` [PATCH v2 0/2] iio: imu: inv_icm42600: Add support for icm42631 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=20221110192933.13616-1-grecojay@amazon.com \
--to=grecojay@amazon.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=jmaneyrol@invensense.com \
--cc=jorcrous@amazon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.