Kconfig 4.3 KB

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