Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
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
Message-ID: <20200810093257.65929-1-alexandru.tachici@analog.com>
MIME-Version: 1.0
Content-Type: text/plain
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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