Kconfig 5.1 KB

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