2 # Industrial I/O subsytem configuration
6 tristate "Industrial I/O support"
7 depends on GENERIC_HARDIRQS
9 The industrial I/O subsystem provides a unified framework for
10 drivers for many different types of embedded sensors using a
11 number of different physical interfaces (i2c, spi, etc). See
12 Documentation/iio for more information.
17 bool "Enable buffer support within IIO"
19 Provide core support for various buffer based data
26 tristate "Industrial I/O buffering based on kfifo"
28 A simple fifo based on kfifo. Use this if you want a fifo
29 rather than a ring buffer. Note that this currently provides
30 no buffer events so it is up to userspace to work out how
31 often to read from the buffer.
33 config IIO_TRIGGERED_BUFFER
38 Provides helper functions for setting up triggered buffers.
43 boolean "Enable triggered sampling support"
45 Provides IIO core support for triggers. Currently these
46 are used to initialize capture of samples to push into
47 ring buffers. The triggers are effectively a 'capture
50 config IIO_CONSUMERS_PER_TRIGGER
51 int "Maximum number of consumers per trigger"
52 depends on IIO_TRIGGER
55 This value controls the maximum number of consumers that a
56 given trigger may handle. Default is 2.
58 source "drivers/iio/adc/Kconfig"
59 source "drivers/iio/amplifiers/Kconfig"
60 source "drivers/iio/light/Kconfig"
61 source "drivers/iio/frequency/Kconfig"
62 source "drivers/iio/dac/Kconfig"