From: Gustavo Silva <gustavograzs@gmail.com>
To: Alex Lanzano <lanzano.alex@gmail.com>,
Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
Gustavo Silva <gustavograzs@gmail.com>
Subject: [PATCH 0/3] BMI270 data ready interrupt support
Date: Wed, 19 Feb 2025 20:54:44 -0300 [thread overview]
Message-ID: <20250219-bmi270-irq-v1-0-145d02bbca3b@gmail.com> (raw)
This series adds support for data ready interrupt to the BMI270 driver
using one of the available interrupt pins.
Additionally, this series includes some cleanups to simplify and improve
consistency across the driver.
Signed-off-by: Gustavo Silva <gustavograzs@gmail.com>
---
Gustavo Silva (3):
iio: imu: bmi270: move private struct declaration to source file
iio: imu: bmi270: rename variable bmi270_device to data
iio: imu: bmi270: add support for data ready interrupt trigger
drivers/iio/imu/bmi270/bmi270.h | 17 +-
drivers/iio/imu/bmi270/bmi270_core.c | 326 ++++++++++++++++++++++++++++++-----
2 files changed, 281 insertions(+), 62 deletions(-)
---
base-commit: 4c571885898c5c98934d086f2ab11b5e27e4f41f
change-id: 20250219-bmi270-irq-9a2bc41faee3
Best regards,
--
Gustavo Silva <gustavograzs@gmail.com>
next reply other threads:[~2025-02-19 23:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-19 23:54 Gustavo Silva [this message]
2025-02-19 23:54 ` [PATCH 1/3] iio: imu: bmi270: move private struct declaration to source file Gustavo Silva
2025-02-22 16:25 ` Alex Lanzano
2025-02-22 17:28 ` Jonathan Cameron
2025-02-19 23:54 ` [PATCH 2/3] iio: imu: bmi270: rename variable bmi270_device to data Gustavo Silva
2025-02-22 16:39 ` Alex Lanzano
2025-02-22 17:31 ` Jonathan Cameron
2025-02-19 23:54 ` [PATCH 3/3] iio: imu: bmi270: add support for data ready interrupt trigger Gustavo Silva
2025-02-22 21:05 ` Alex Lanzano
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=20250219-bmi270-irq-v1-0-145d02bbca3b@gmail.com \
--to=gustavograzs@gmail.com \
--cc=jic23@kernel.org \
--cc=lanzano.alex@gmail.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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