From: Nishant Malpani <nish.malpani25@gmail.com>
To: jic23@kernel.org, robh+dt@kernel.org
Cc: dragos.bogdan@analog.com, darius.berghe@analog.com,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org,
Nishant Malpani <nish.malpani25@gmail.com>
Subject: [PATCH 0/3] iio: gyro: adxrs290: Add triggered buffer & debugfs support
Date: Tue, 25 Aug 2020 18:17:08 +0530 [thread overview]
Message-ID: <20200825124711.11455-1-nish.malpani25@gmail.com> (raw)
Introduce DATA_RDY trigger for triggered buffer setup; this enables continuous
data capture. Additionally, add support for direct register access using the debugfs
iio interface.
The device-tree bindings documentation illustrates an example of using a GPIO irq
line to trigger a data capture.
Nishant Malpani (3):
iio: gyro: adxrs290: Add triggered buffer support
dt-bindings: iio: gyro: adxrs290: Add required interrupts property
iio: gyro: adxrs290: Add debugfs register access support
.../bindings/iio/gyroscope/adi,adxrs290.yaml | 8 +
drivers/iio/gyro/Kconfig | 2 +
drivers/iio/gyro/adxrs290.c | 291 +++++++++++++++++-
3 files changed, 287 insertions(+), 14 deletions(-)
--
2.20.1
next reply other threads:[~2020-08-25 12:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-25 12:47 Nishant Malpani [this message]
2020-08-25 12:47 ` [PATCH 1/3] iio: gyro: adxrs290: Add triggered buffer support Nishant Malpani
2020-08-26 16:10 ` Andy Shevchenko
2020-09-02 10:31 ` Nishant Malpani
2020-08-29 16:46 ` Jonathan Cameron
2020-09-03 12:37 ` Nishant Malpani
2020-09-06 14:51 ` Jonathan Cameron
2020-08-25 12:47 ` [PATCH 2/3] dt-bindings: iio: gyro: adxrs290: Add required interrupts property Nishant Malpani
2020-08-29 16:48 ` Jonathan Cameron
2020-09-03 12:46 ` Nishant Malpani
2020-08-25 12:47 ` [PATCH 3/3] iio: gyro: adxrs290: Add debugfs register access support Nishant Malpani
2020-08-29 16:51 ` 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=20200825124711.11455-1-nish.malpani25@gmail.com \
--to=nish.malpani25@gmail.com \
--cc=darius.berghe@analog.com \
--cc=devicetree@vger.kernel.org \
--cc=dragos.bogdan@analog.com \
--cc=jic23@kernel.org \
--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.