[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200318110958.8621-5-alexandru.tachici@analog.com>
Date: Wed, 18 Mar 2020 13:09:58 +0200
From: Alexandru Tachici <tachicialex@...il.com>
To: linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: jic23@...nel.org
Subject: [PATCH v3 4/4] iio: accel: adxl372: Update sysfs docs
This patch adds entries in the syfs docs of ADXL372.
Signed-off-by: Stefan Popa <stefan.popa@...log.com>
Signed-off-by: Alexandru Tachici <alexandru.tachici@...log.com>
---
.../ABI/testing/sysfs-bus-iio-accel-adxl372 | 30 +++++++++++++++++++
1 file changed, 30 insertions(+)
create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372
diff --git a/Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372 b/Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372
new file mode 100644
index 000000000000..6be4f57f9520
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372
@@ -0,0 +1,30 @@
+What: /sys/bus/iio/devices/iio:deviceX/hwfifo_peak_mode_enable
+KernelVersion:
+Contact: linux-iio@...r.kernel.org
+Description:
+ This attribute allows to configure the FIFO to store sample
+ sets of impact event peak (x, y, z). As a precondition, all
+ three channels (x, y, z) need to be enabled.
+ Writing 1, peak fifo mode will be enabled, if cleared and
+ all three channels are enabled, sample sets of concurrent
+ 3-axis data will be stored in the FIFO.
+
+What: /sys/bus/iio/devices/iio:deviceX/activity_detect_event
+KernelVersion:
+Contact: linux-iio@...r.kernel.org
+Description:
+ adxl372 works in loop mode. It will loop between activity
+ and inactivity detection mode. The thresh_rising sysfs files
+ found in events/ need to be configured in order to define when
+ the device will mark a sensed acceleration over a period of
+ time as activity. Reads "in_accel_thresh_x_rising".
+
+What: /sys/bus/iio/devices/iio:deviceX/inactivity_detect_event
+KernelVersion:
+Contact: linux-iio@...r.kernel.org
+Description:
+ adxl372 works in loop mode. It will loop between activity
+ and inactivity detection mode. The thresh_falling sysfs files
+ found in events/ need to be configured in order to define when
+ the device will mark a sensed acceleration over a period of
+ time as inactivity. Reads "in_accel_thresh_x_falling".
--
2.20.1
Powered by blists - more mailing lists