117 lines · plain
1# SPDX-License-Identifier: GPL-2.0-only2#3# Industrial I/O subsystem configuration4#5 6menuconfig IIO7 tristate "Industrial I/O support"8 help9 The industrial I/O subsystem provides a unified framework for10 drivers for many different types of embedded sensors using a11 number of different physical interfaces (i2c, spi, etc).12 13if IIO14 15config IIO_BUFFER16 bool "Enable buffer support within IIO"17 select DMA_SHARED_BUFFER18 help19 Provide core support for various buffer based data20 acquisition methods.21 22if IIO_BUFFER23 source "drivers/iio/buffer/Kconfig"24endif # IIO_BUFFER25 26config IIO_CONFIGFS27 tristate "Enable IIO configuration via configfs"28 select CONFIGFS_FS29 help30 This allows configuring various IIO bits through configfs31 (e.g. software triggers). For more info see32 Documentation/iio/iio_configfs.rst.33 34config IIO_GTS_HELPER35 tristate36 37config IIO_TRIGGER38 bool "Enable triggered sampling support"39 help40 Provides IIO core support for triggers. Currently these41 are used to initialize capture of samples to push into42 buffers. The triggers are effectively a 'capture43 data now' interrupt.44 45config IIO_CONSUMERS_PER_TRIGGER46 int "Maximum number of consumers per trigger"47 depends on IIO_TRIGGER48 default "2"49 help50 This value controls the maximum number of consumers that a51 given trigger may handle. Default is 2.52 53config IIO_SW_DEVICE54 tristate "Enable software IIO device support"55 select IIO_CONFIGFS56 help57 Provides IIO core support for software devices. A software58 device can be created via configfs or directly by a driver59 using the API provided.60 61config IIO_SW_TRIGGER62 tristate "Enable software triggers support"63 select IIO_CONFIGFS64 help65 Provides IIO core support for software triggers. A software66 trigger can be created via configfs or directly by a driver67 using the API provided.68 69config IIO_TRIGGERED_EVENT70 tristate "Enable triggered events support"71 select IIO_TRIGGER72 help73 Provides helper functions for setting up triggered events.74 75config IIO_BACKEND76 tristate77 help78 Framework to handle complex IIO aggregate devices. The typical79 architecture that can make use of this framework is to have one80 device as the frontend device which can be "linked" against one or81 multiple backend devices. The framework then makes it easy to get82 and control such backend devices.83 84source "drivers/iio/accel/Kconfig"85source "drivers/iio/adc/Kconfig"86source "drivers/iio/addac/Kconfig"87source "drivers/iio/afe/Kconfig"88source "drivers/iio/amplifiers/Kconfig"89source "drivers/iio/cdc/Kconfig"90source "drivers/iio/chemical/Kconfig"91source "drivers/iio/common/Kconfig"92source "drivers/iio/dac/Kconfig"93source "drivers/iio/dummy/Kconfig"94source "drivers/iio/filter/Kconfig"95source "drivers/iio/frequency/Kconfig"96source "drivers/iio/gyro/Kconfig"97source "drivers/iio/health/Kconfig"98source "drivers/iio/humidity/Kconfig"99source "drivers/iio/imu/Kconfig"100source "drivers/iio/light/Kconfig"101source "drivers/iio/magnetometer/Kconfig"102source "drivers/iio/multiplexer/Kconfig"103source "drivers/iio/orientation/Kconfig"104source "drivers/iio/test/Kconfig"105if IIO_TRIGGER106 source "drivers/iio/trigger/Kconfig"107endif #IIO_TRIGGER108source "drivers/iio/position/Kconfig"109source "drivers/iio/potentiometer/Kconfig"110source "drivers/iio/potentiostat/Kconfig"111source "drivers/iio/pressure/Kconfig"112source "drivers/iio/proximity/Kconfig"113source "drivers/iio/resolver/Kconfig"114source "drivers/iio/temperature/Kconfig"115 116endif # IIO117