7f3a1fb998
The original posting of this driver led to a discussion in which it was commented that a better system was needed for dealing with the many possible periodic interrupt sources available on some SoCs. Unfortunately that is a big task and as far as I know, no-one has taken it on as yet. So in the meantime this driver is still in here. Signed-off-by: Jonathan Cameron <jic23@cam.ac.uk> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
48 lines
1.3 KiB
Plaintext
48 lines
1.3 KiB
Plaintext
#
|
|
# Industrial I/O subsytem configuration
|
|
#
|
|
|
|
menuconfig IIO
|
|
tristate "Industrial I/O support"
|
|
---help---
|
|
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/industrialio for more information.
|
|
if IIO
|
|
|
|
config IIO_RING_BUFFER
|
|
bool "Enable ring buffer support within IIO"
|
|
help
|
|
Provide core support for various ring buffer based data
|
|
acquisition methods.
|
|
|
|
if IIO_RING_BUFFER
|
|
|
|
config IIO_SW_RING
|
|
tristate "Industrial I/O lock free software ring"
|
|
help
|
|
example software ring buffer implementation. The design aim
|
|
of this particular realization was to minize write locking
|
|
with the intention that some devices would be able to write
|
|
in interrupt context.
|
|
|
|
endif # IIO_RINGBUFFER
|
|
|
|
config IIO_TRIGGER
|
|
boolean "Enable triggered sampling support"
|
|
help
|
|
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.
|
|
|
|
|
|
source "drivers/staging/iio/accel/Kconfig"
|
|
source "drivers/staging/iio/adc/Kconfig"
|
|
source "drivers/staging/iio/light/Kconfig"
|
|
|
|
source "drivers/staging/iio/trigger/Kconfig"
|
|
|
|
endif # IIO
|