This series adds the posibility 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 and rising_period in events/ dir. 2. Create sysfs files for thresh_falling_value and thresh_rising_value for each axis. 3. Set INT1 reg for acitivity/inactivity and push event code in events fifo on irq. 4. Add additional ABIs in order to explain the user that setting values in the events/ sysfs files also changes device behaviour. 5. Update sysfs docs: renames, added two new entries for the activity_detect_event/ inactivity_detect_event Alexandru Tachici (5): iio: accel: adxl372: add sysfs for time registers iio: accel: adxl372: Add sysfs for g thresholds iio: accel: adxl372: add iio events iio: accel: adxl372: add additional events ABIs iio: accel: adxl372: Update sysfs docs Stefan Popa (1): iio: accel: adxl372: Add support for FIFO peak mode 1. Device FIFO can now be set in peak mode and only over the threshold accelerations will be stored. Changelog V1 -> V2: - switched from custom sysfs for setting the accel thres/timings to standard events interface. - renamed fifo_peak_mode_enable to buffer_peak_mode_enable - on activity/inactivity, event codes are now pushed in the events FIFO - added additional custom sysfs for explaining that setting values in the events/ sysfs files will change the device's behaviour. .../ABI/testing/sysfs-bus-iio-accel-adxl372 | 30 ++ drivers/iio/accel/adxl372.c | 265 +++++++++++++++++- 2 files changed, 293 insertions(+), 2 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372 -- 2.20.1
