|author||Jonathan Cameron <email@example.com>||2012-04-25 15:54:59 +0100|
|committer||Greg Kroah-Hartman <firstname.lastname@example.org>||2012-04-25 11:11:38 -0700|
IIO: Move the core files to drivers/iio
Take the core support + the kfifo buffer implentation out of staging. Whilst we are far from done in improving this subsystem it is now at a stage where the userspae interfaces (provided by the core) can be considered stable. Drivers will follow over a longer time scale. Signed-off-by: Jonathan Cameron <email@example.com> Signed-off-by: Greg Kroah-Hartman <firstname.lastname@example.org>
Diffstat (limited to 'drivers/iio/Kconfig')
1 files changed, 51 insertions, 0 deletions
diff --git a/drivers/iio/Kconfig b/drivers/iio/Kconfig
new file mode 100644
@@ -0,0 +1,51 @@
+# Industrial I/O subsytem configuration
+ tristate "Industrial I/O support"
+ depends on GENERIC_HARDIRQS
+ The industrial I/O subsystem provides a unified framework for
+ drivers for many different types of embedded sensors using a
+ number of different physical interfaces (i2c, spi, etc). See
+ Documentation/iio for more information.
+ bool "Enable buffer support within IIO"
+ Provide core support for various buffer based data
+ acquisition methods.
+ select IIO_TRIGGER
+ tristate "Industrial I/O buffering based on kfifo"
+ A simple fifo based on kfifo. Use this if you want a fifo
+ rather than a ring buffer. Note that this currently provides
+ no buffer events so it is up to userspace to work out how
+ often to read from the buffer.
+endif # IIO_BUFFER
+ boolean "Enable triggered sampling support"
+ Provides IIO core support for triggers. Currently these
+ are used to initialize capture of samples to push into
+ ring buffers. The triggers are effectively a 'capture
+ data now' interrupt.
+ int "Maximum number of consumers per trigger"
+ depends on IIO_TRIGGER
+ default "2"
+ This value controls the maximum number of consumers that a
+ given trigger may handle. Default is 2.
+endif # IIO