From: inv.git-commit@tdk.com
To: jic23@kernel.org, robh@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org
Cc: lars@metafoo.de, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org,
Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
Subject: [PATCH 0/2] iio: imu: inv_icm42600: add support of ICM-42686-P
Date: Mon, 22 Apr 2024 15:22:38 +0000 [thread overview]
Message-ID: <20240422152240.85974-1-inv.git-commit@tdk.com> (raw)
From: Jean-Baptiste Maneyrol <jean-baptiste.maneyrol@tdk.com>
ICM-42686-P is a special chip supporting high Full Scale Range (FSR)
values. Up to +/-32G for accel and +/-4000dps for gyro.
For supporting this chip, we are using dynamic scales tables set at init.
Introduce a new sensor state structure for olding pointer to the dynamic
table plus the already used timestamp structure.
Jean-Baptiste Maneyrol (2):
dt-bindings: iio: imu: add icm42686 inside inv_icm42600
iio: imu: inv_icm42600: add support of ICM-42686-P
.../bindings/iio/imu/invensense,icm42600.yaml | 1 +
drivers/iio/imu/inv_icm42600/inv_icm42600.h | 35 ++++++++
.../iio/imu/inv_icm42600/inv_icm42600_accel.c | 75 ++++++++++++-----
.../imu/inv_icm42600/inv_icm42600_buffer.c | 15 ++--
.../iio/imu/inv_icm42600/inv_icm42600_core.c | 20 +++++
.../iio/imu/inv_icm42600/inv_icm42600_gyro.c | 84 ++++++++++++++-----
.../iio/imu/inv_icm42600/inv_icm42600_i2c.c | 3 +
.../iio/imu/inv_icm42600/inv_icm42600_spi.c | 3 +
8 files changed, 193 insertions(+), 43 deletions(-)
--
2.34.1
next reply other threads:[~2024-04-22 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 15:22 inv.git-commit [this message]
2024-04-22 15:22 ` [PATCH 1/2] dt-bindings: iio: imu: add icm42686 inside inv_icm42600 inv.git-commit
2024-04-23 14:27 ` Rob Herring
2024-04-22 15:22 ` [PATCH 2/2] iio: imu: inv_icm42600: add support of ICM-42686-P inv.git-commit
2024-04-28 16:03 ` 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=20240422152240.85974-1-inv.git-commit@tdk.com \
--to=inv.git-commit@tdk.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jean-baptiste.maneyrol@tdk.com \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=robh@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.