Kconfig 3.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114
  1. #
  2. # I2C subsystem configuration
  3. #
  4. menuconfig I2C
  5. tristate "I2C support"
  6. depends on HAS_IOMEM
  7. select RT_MUTEXES
  8. ---help---
  9. I2C (pronounce: I-square-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. if I2C
  21. config I2C_BOARDINFO
  22. boolean
  23. default y
  24. config I2C_COMPAT
  25. boolean "Enable compatibility bits for old user-space"
  26. default y
  27. help
  28. Say Y here if you intend to run lm-sensors 3.1.1 or older, or any
  29. other user-space package which expects i2c adapters to be class
  30. devices. If you don't know, say Y.
  31. config I2C_CHARDEV
  32. tristate "I2C device interface"
  33. help
  34. Say Y here to use i2c-* device files, usually found in the /dev
  35. directory on your system. They make it possible to have user-space
  36. programs use the I2C bus. Information on how to do this is
  37. contained in the file <file:Documentation/i2c/dev-interface>.
  38. This support is also available as a module. If so, the module
  39. will be called i2c-dev.
  40. config I2C_MUX
  41. tristate "I2C bus multiplexing support"
  42. depends on EXPERIMENTAL
  43. help
  44. Say Y here if you want the I2C core to support the ability to
  45. handle multiplexed I2C bus topologies, by presenting each
  46. multiplexed segment as a I2C adapter.
  47. This support is also available as a module. If so, the module
  48. will be called i2c-mux.
  49. source drivers/i2c/muxes/Kconfig
  50. config I2C_HELPER_AUTO
  51. bool "Autoselect pertinent helper modules"
  52. default y
  53. help
  54. Some I2C bus drivers require so-called "I2C algorithm" modules
  55. to work. These are basically software-only abstractions of generic
  56. I2C interfaces. This option will autoselect them so that you don't
  57. have to care.
  58. Unselect this only if you need to enable additional helper
  59. modules, for example for use with external I2C bus drivers.
  60. In doubt, say Y.
  61. config I2C_SMBUS
  62. tristate "SMBus-specific protocols" if !I2C_HELPER_AUTO
  63. help
  64. Say Y here if you want support for SMBus extensions to the I2C
  65. specification. At the moment, the only supported extension is
  66. the SMBus alert protocol.
  67. This support is also available as a module. If so, the module
  68. will be called i2c-smbus.
  69. source drivers/i2c/algos/Kconfig
  70. source drivers/i2c/busses/Kconfig
  71. config I2C_DEBUG_CORE
  72. bool "I2C Core debugging messages"
  73. help
  74. Say Y here if you want the I2C core to produce a bunch of debug
  75. messages to the system log. Select this if you are having a
  76. problem with I2C support and want to see more of what is going on.
  77. config I2C_DEBUG_ALGO
  78. bool "I2C Algorithm debugging messages"
  79. help
  80. Say Y here if you want the I2C algorithm drivers to produce a bunch
  81. of debug messages to the system log. Select this if you are having
  82. a problem with I2C support and want to see more of what is going
  83. on.
  84. config I2C_DEBUG_BUS
  85. bool "I2C Bus debugging messages"
  86. help
  87. Say Y here if you want the I2C bus drivers to produce a bunch of
  88. debug messages to the system log. Select this if you are having
  89. a problem with I2C support and want to see more of what is going
  90. on.
  91. endif # I2C