Kconfig 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091929394959697
  1. #
  2. # Industrial I/O subsystem configuration
  3. #
  4. menuconfig IIO
  5. tristate "Industrial I/O support"
  6. help
  7. The industrial I/O subsystem provides a unified framework for
  8. drivers for many different types of embedded sensors using a
  9. number of different physical interfaces (i2c, spi, etc).
  10. if IIO
  11. config IIO_BUFFER
  12. bool "Enable buffer support within IIO"
  13. help
  14. Provide core support for various buffer based data
  15. acquisition methods.
  16. if IIO_BUFFER
  17. source "drivers/iio/buffer/Kconfig"
  18. endif # IIO_BUFFER
  19. config IIO_CONFIGFS
  20. tristate "Enable IIO configuration via configfs"
  21. select CONFIGFS_FS
  22. help
  23. This allows configuring various IIO bits through configfs
  24. (e.g. software triggers). For more info see
  25. Documentation/iio/iio_configfs.txt.
  26. config IIO_TRIGGER
  27. bool "Enable triggered sampling support"
  28. help
  29. Provides IIO core support for triggers. Currently these
  30. are used to initialize capture of samples to push into
  31. buffers. The triggers are effectively a 'capture
  32. data now' interrupt.
  33. config IIO_CONSUMERS_PER_TRIGGER
  34. int "Maximum number of consumers per trigger"
  35. depends on IIO_TRIGGER
  36. default "2"
  37. help
  38. This value controls the maximum number of consumers that a
  39. given trigger may handle. Default is 2.
  40. config IIO_SW_DEVICE
  41. tristate "Enable software IIO device support"
  42. select IIO_CONFIGFS
  43. help
  44. Provides IIO core support for software devices. A software
  45. device can be created via configfs or directly by a driver
  46. using the API provided.
  47. config IIO_SW_TRIGGER
  48. tristate "Enable software triggers support"
  49. select IIO_CONFIGFS
  50. help
  51. Provides IIO core support for software triggers. A software
  52. trigger can be created via configfs or directly by a driver
  53. using the API provided.
  54. config IIO_TRIGGERED_EVENT
  55. tristate
  56. select IIO_TRIGGER
  57. help
  58. Provides helper functions for setting up triggered events.
  59. source "drivers/iio/accel/Kconfig"
  60. source "drivers/iio/adc/Kconfig"
  61. source "drivers/iio/amplifiers/Kconfig"
  62. source "drivers/iio/chemical/Kconfig"
  63. source "drivers/iio/common/Kconfig"
  64. source "drivers/iio/counter/Kconfig"
  65. source "drivers/iio/dac/Kconfig"
  66. source "drivers/iio/dummy/Kconfig"
  67. source "drivers/iio/frequency/Kconfig"
  68. source "drivers/iio/gyro/Kconfig"
  69. source "drivers/iio/health/Kconfig"
  70. source "drivers/iio/humidity/Kconfig"
  71. source "drivers/iio/imu/Kconfig"
  72. source "drivers/iio/light/Kconfig"
  73. source "drivers/iio/magnetometer/Kconfig"
  74. source "drivers/iio/multiplexer/Kconfig"
  75. source "drivers/iio/orientation/Kconfig"
  76. if IIO_TRIGGER
  77. source "drivers/iio/trigger/Kconfig"
  78. endif #IIO_TRIGGER
  79. source "drivers/iio/potentiometer/Kconfig"
  80. source "drivers/iio/potentiostat/Kconfig"
  81. source "drivers/iio/pressure/Kconfig"
  82. source "drivers/iio/proximity/Kconfig"
  83. source "drivers/iio/temperature/Kconfig"
  84. endif # IIO