Kconfig 2.8 KB

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