Kconfig 4.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148
  1. #
  2. # I2C subsystem configuration
  3. #
  4. menu "I2C support"
  5. config I2C
  6. tristate "I2C support"
  7. select RT_MUTEXES
  8. ---help---
  9. I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
  10. many micro controller applications and developed by Philips. SMBus,
  11. or System Management Bus is a subset of the I2C protocol. More
  12. information is contained in the directory <file:Documentation/i2c/>,
  13. especially in the file called "summary" there.
  14. Both I2C and SMBus are supported here. You will need this for
  15. hardware sensors support, and also for Video For Linux support.
  16. If you want I2C support, you should say Y here and also to the
  17. specific driver for your bus adapter(s) below.
  18. This I2C support can also be built as a module. If so, the module
  19. will be called i2c-core.
  20. config ACPI_I2C_OPREGION
  21. bool "ACPI I2C Operation region support"
  22. depends on I2C=y && ACPI
  23. default y
  24. help
  25. Say Y here if you want to enable ACPI I2C operation region support.
  26. Operation Regions allow firmware (BIOS) code to access I2C slave devices,
  27. such as smart batteries through an I2C host controller driver.
  28. if I2C
  29. config I2C_BOARDINFO
  30. bool
  31. default y
  32. config I2C_COMPAT
  33. bool "Enable compatibility bits for old user-space"
  34. default y
  35. help
  36. Say Y here if you intend to run lm-sensors 3.1.1 or older, or any
  37. other user-space package which expects i2c adapters to be class
  38. devices. If you don't know, say Y.
  39. config I2C_CHARDEV
  40. tristate "I2C device interface"
  41. help
  42. Say Y here to use i2c-* device files, usually found in the /dev
  43. directory on your system. They make it possible to have user-space
  44. programs use the I2C bus. Information on how to do this is
  45. contained in the file <file:Documentation/i2c/dev-interface>.
  46. This support is also available as a module. If so, the module
  47. will be called i2c-dev.
  48. config I2C_MUX
  49. tristate "I2C bus multiplexing support"
  50. help
  51. Say Y here if you want the I2C core to support the ability to
  52. handle multiplexed I2C bus topologies, by presenting each
  53. multiplexed segment as a I2C adapter.
  54. This support is also available as a module. If so, the module
  55. will be called i2c-mux.
  56. source drivers/i2c/muxes/Kconfig
  57. config I2C_HELPER_AUTO
  58. bool "Autoselect pertinent helper modules"
  59. default y
  60. help
  61. Some I2C bus drivers require so-called "I2C algorithm" modules
  62. to work. These are basically software-only abstractions of generic
  63. I2C interfaces. This option will autoselect them so that you don't
  64. have to care.
  65. Unselect this only if you need to enable additional helper
  66. modules, for example for use with external I2C bus drivers.
  67. In doubt, say Y.
  68. config I2C_SMBUS
  69. tristate "SMBus-specific protocols" if !I2C_HELPER_AUTO
  70. help
  71. Say Y here if you want support for SMBus extensions to the I2C
  72. specification. At the moment, the only supported extension is
  73. the SMBus alert protocol.
  74. This support is also available as a module. If so, the module
  75. will be called i2c-smbus.
  76. source drivers/i2c/algos/Kconfig
  77. source drivers/i2c/busses/Kconfig
  78. config I2C_STUB
  79. tristate "I2C/SMBus Test Stub"
  80. depends on m
  81. default 'n'
  82. help
  83. This module may be useful to developers of SMBus client drivers,
  84. especially for certain kinds of sensor chips.
  85. If you do build this module, be sure to read the notes and warnings
  86. in <file:Documentation/i2c/i2c-stub>.
  87. If you don't know what to do here, definitely say N.
  88. config I2C_SLAVE
  89. bool "I2C slave support"
  90. if I2C_SLAVE
  91. config I2C_SLAVE_EEPROM
  92. tristate "I2C eeprom slave driver"
  93. endif
  94. config I2C_DEBUG_CORE
  95. bool "I2C Core debugging messages"
  96. help
  97. Say Y here if you want the I2C core to produce a bunch of debug
  98. messages to the system log. Select this if you are having a
  99. problem with I2C support and want to see more of what is going on.
  100. config I2C_DEBUG_ALGO
  101. bool "I2C Algorithm debugging messages"
  102. help
  103. Say Y here if you want the I2C algorithm drivers to produce a bunch
  104. of debug messages to the system log. Select this if you are having
  105. a problem with I2C support and want to see more of what is going
  106. on.
  107. config I2C_DEBUG_BUS
  108. bool "I2C Bus debugging messages"
  109. depends on HAS_IOMEM
  110. help
  111. Say Y here if you want the I2C bus drivers to produce a bunch of
  112. debug messages to the system log. Select this if you are having
  113. a problem with I2C support and want to see more of what is going
  114. on.
  115. endif # I2C
  116. endmenu