linux-kernel - Re: [PATCH 06/13] iio: buffer: add hardware triggered buffer support

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: <20240112123711.0000422a@Huawei.com>
Date: Fri, 12 Jan 2024 12:37:11 +0000
From: Jonathan Cameron <Jonathan.Cameron@...wei.com>
To: David Lechner <dlechner@...libre.com>
CC: Mark Brown <broonie@...nel.org>, Jonathan Cameron <jic23@...nel.org>, Rob
 Herring <robh+dt@...nel.org>, Krzysztof Kozlowski
	<krzysztof.kozlowski+dt@...aro.org>, Conor Dooley <conor+dt@...nel.org>,
	Michael Hennerich <michael.hennerich@...log.com>, Nuno Sá <nuno.sa@...log.com>, Frank Rowand
	<frowand.list@...il.com>, Thierry Reding <thierry.reding@...il.com>, Uwe
 Kleine-König <u.kleine-koenig@...gutronix.de>, "Jonathan
 Corbet" <corbet@....net>, <linux-spi@...r.kernel.org>,
	<linux-iio@...r.kernel.org>, <devicetree@...r.kernel.org>,
	<linux-doc@...r.kernel.org>, <linux-pwm@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 06/13] iio: buffer: add hardware triggered buffer
 support

On Wed, 10 Jan 2024 13:49:47 -0600
David Lechner <dlechner@...libre.com> wrote:

> This adds a new mode INDIO_HW_BUFFER_TRIGGERED to the IIO subsystem.
> 
> This mode is essentially the hardware version of INDIO_BUFFER_TRIGGERED
> where the trigger has the semantics of INDIO_HARDWARE_TRIGGERED and the
> buffer has the semantics of INDIO_BUFFER_HARDWARE.
> 
> So basically INDIO_HW_BUFFER_TRIGGERED is the same as
> INDIO_BUFFER_HARDWARE except that it also enables the trigger when the
> buffer is enabled.

If the trigger isn't routeable to multiple devices we normally don't
make it visible at all.

I'm not yet understanding what a trigger actually means in this case.
Why do you need it to be userspace configurable?

J