From: Nishant Malpani <nish.malpani25@gmail.com>
To: jic23@kernel.org, robh+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
devicetree@vger.kernel.org, andy.shevchenko@gmail.com,
Nishant Malpani <nish.malpani25@gmail.com>
Subject: [RESEND PATCH v3 0/3] iio: gyro: adxrs290: Add triggered buffer & debugfs support
Date: Thu, 10 Sep 2020 23:34:47 +0530 [thread overview]
Message-ID: <20200910180450.29696-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 interrupts support
iio: gyro: adxrs290: Add debugfs register access support
.../bindings/iio/gyroscope/adi,adxrs290.yaml | 6 +
drivers/iio/gyro/Kconfig | 2 +
drivers/iio/gyro/adxrs290.c | 237 ++++++++++++++++--
3 files changed, 231 insertions(+), 14 deletions(-)
--
2.20.1
next reply other threads:[~2020-09-10 18:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 18:04 Nishant Malpani [this message]
2020-09-10 18:04 ` [RESEND PATCH v3 1/3] iio: gyro: adxrs290: Add triggered buffer support Nishant Malpani
2020-09-10 18:04 ` [RESEND PATCH v3 2/3] dt-bindings: iio: gyro: adxrs290: Add interrupts support Nishant Malpani
2020-09-13 9:54 ` Jonathan Cameron
2020-09-10 18:04 ` [RESEND PATCH v3 3/3] iio: gyro: adxrs290: Add debugfs register access support Nishant Malpani
2020-09-11 8:14 ` [RESEND PATCH v3 0/3] iio: gyro: adxrs290: Add triggered buffer & debugfs support Jonathan Cameron
2020-09-13 9:52 ` 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=20200910180450.29696-1-nish.malpani25@gmail.com \
--to=nish.malpani25@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--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 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).