linux-kernel - Re: [PATCH v5 2/2] iio: accel: adxl372: Add additional trigger ABI docs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200829183411.58cac8d7@archlinux>
Date:   Sat, 29 Aug 2020 18:34:11 +0100
From:   Jonathan Cameron <jic23@...nel.org>
To:     <alexandru.tachici@...log.com>
Cc:     <linux-iio@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 2/2] iio: accel: adxl372: Add additional trigger ABI
 docs

On Mon, 10 Aug 2020 12:32:57 +0300
<alexandru.tachici@...log.com> wrote:

> From: Alexandru Tachici <alexandru.tachici@...log.com>
> 
> Document use of additional trigger supplied by driver.
> 
> Signed-off-by: Alexandru Tachici <alexandru.tachici@...log.com>
> ---
>  Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372 | 7 +++++++
>  1 file changed, 7 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..47e34f865ca1
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-bus-iio-accel-adxl372
> @@ -0,0 +1,7 @@
> +What:		/sys/bus/iio/devices/triggerX/name = "adxl372-devX-peak"
> +KernelVersion:
> +Contact:	linux-iio@...r.kernel.org
> +Description:
> +		The adxl372 accelerometer kernel module provides an additional trigger,
> +		which sets the device in a mode in which it will record only the peak acceleration
> +		sensed over the set period of time in the events sysfs.

Innovative use of docs.  I was thinking about adding specific
docs for the event/* things that are tied up to this.

If you think that is useful, perhaps a follow up patch?