From: <alexandru.tachici@analog.com>
To: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <jic23@kernel.org>
Subject: [PATCH v5 0/2] iio: accel: adxl372: Add support for FIFO peak mode
Date: Mon, 10 Aug 2020 12:32:55 +0300 [thread overview]
Message-ID: <20200810093257.65929-1-alexandru.tachici@analog.com> (raw)
From: Alexandru Tachici <alexandru.tachici@analog.com>
This series adds the possibility to configure
the device, from sysfs, to work in peak mode. This enables
adxl372 to capture only over threshold accelerations.
1. Create sysfs files for falling_period/rising_period
and thresh_falling_value/thresh_rising_value in events/ dir.
Set INT1 reg for activity/inactivity and push
event code in events fifo on irq.
2. Document use of iio events sysfs files.
Alexandru Tachici (1):
iio: accel: adxl372: Add additional trigger ABI docs
Stefan Popa (1):
iio: accel: adxl372: Add support for FIFO peak mode
Changelog v4 -> v5:
- squash iio event interface patch into peak mode patch
- move patch to 100 lines length
- use((x) & BIT(0)) construct for define ADXL372_Y_AXIS_EN(x)
- add ABI docs to explain the use of the additional trigger
.../ABI/testing/sysfs-bus-iio-accel-adxl372 | 7 +
drivers/iio/accel/adxl372.c | 302 +++++++++++++++++-
2 files changed, 301 insertions(+), 8 deletions(-)
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372
--
2.20.1
next reply other threads:[~2020-08-10 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-10 9:32 alexandru.tachici [this message]
2020-08-10 9:32 ` [PATCH v5 1/2] iio: accel: adxl372: Add support for FIFO peak mode alexandru.tachici
2020-08-29 17:43 ` Jonathan Cameron
2020-09-01 18:40 ` Jonathan Cameron
2020-09-03 18:29 ` Jonathan Cameron
2020-08-10 9:32 ` [PATCH v5 2/2] iio: accel: adxl372: Add additional trigger ABI docs alexandru.tachici
2020-08-29 17:34 ` 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=20200810093257.65929-1-alexandru.tachici@analog.com \
--to=alexandru.tachici@analog.com \
--cc=jic23@kernel.org \
--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 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.