8548a63b37
For generic IIO trigger implementations we already have a sub-directory, but the generic buffer implementations currently reside in the IIO top-level directory. The main reason is that things have historically grown into this form. With more generic buffer implementations on its way now is the perfect time to clean this up and introduce a sub-directory for generic buffer implementations to avoid too much clutter in the top-level directory. Signed-off-by: Lars-Peter Clausen <lars@metafoo.de> Signed-off-by: Jonathan Cameron <jic23@kernel.org>
24 lines
730 B
Text
24 lines
730 B
Text
#
|
|
# Industrial I/O generic buffer implementations
|
|
#
|
|
# When adding new entries keep the list in alphabetical order
|
|
|
|
config IIO_BUFFER_CB
|
|
tristate "IIO callback buffer used for push in-kernel interfaces"
|
|
help
|
|
Should be selected by any drivers that do in-kernel push
|
|
usage. That is, those where the data is pushed to the consumer.
|
|
|
|
config IIO_KFIFO_BUF
|
|
tristate "Industrial I/O buffering based on kfifo"
|
|
help
|
|
A simple fifo based on kfifo. Note that this currently provides
|
|
no buffer events so it is up to userspace to work out how
|
|
often to read from the buffer.
|
|
|
|
config IIO_TRIGGERED_BUFFER
|
|
tristate
|
|
select IIO_TRIGGER
|
|
select IIO_KFIFO_BUF
|
|
help
|
|
Provides helper functions for setting up triggered buffers.
|