Kconfig 3.1 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374757677787980818283848586878889909192939495969798
  1. #
  2. # I2C subsystem configuration
  3. #
  4. menuconfig I2C
  5. tristate "I2C support"
  6. depends on HAS_IOMEM
  7. ---help---
  8. I2C (pronounce: I-square-C) is a slow serial bus protocol used in
  9. many micro controller applications and developed by Philips. SMBus,
  10. or System Management Bus is a subset of the I2C protocol. More
  11. information is contained in the directory <file:Documentation/i2c/>,
  12. especially in the file called "summary" there.
  13. Both I2C and SMBus are supported here. You will need this for
  14. hardware sensors support, and also for Video For Linux support.
  15. If you want I2C support, you should say Y here and also to the
  16. specific driver for your bus adapter(s) below.
  17. This I2C support can also be built as a module. If so, the module
  18. will be called i2c-core.
  19. if I2C
  20. config I2C_BOARDINFO
  21. boolean
  22. default y
  23. config I2C_COMPAT
  24. boolean "Enable compatibility bits for old user-space"
  25. default y
  26. help
  27. Say Y here if you intend to run lm-sensors 3.1.1 or older, or any
  28. other user-space package which expects i2c adapters to be class
  29. devices. If you don't know, say Y.
  30. config I2C_CHARDEV
  31. tristate "I2C device interface"
  32. help
  33. Say Y here to use i2c-* device files, usually found in the /dev
  34. directory on your system. They make it possible to have user-space
  35. programs use the I2C bus. Information on how to do this is
  36. contained in the file <file:Documentation/i2c/dev-interface>.
  37. This support is also available as a module. If so, the module
  38. will be called i2c-dev.
  39. config I2C_HELPER_AUTO
  40. bool "Autoselect pertinent helper modules"
  41. default y
  42. help
  43. Some I2C bus drivers require so-called "I2C algorithm" modules
  44. to work. These are basically software-only abstractions of generic
  45. I2C interfaces. This option will autoselect them so that you don't
  46. have to care.
  47. Unselect this only if you need to enable additional helper
  48. modules, for example for use with external I2C bus drivers.
  49. In doubt, say Y.
  50. source drivers/i2c/algos/Kconfig
  51. source drivers/i2c/busses/Kconfig
  52. source drivers/i2c/chips/Kconfig
  53. config I2C_DEBUG_CORE
  54. bool "I2C Core debugging messages"
  55. help
  56. Say Y here if you want the I2C core to produce a bunch of debug
  57. messages to the system log. Select this if you are having a
  58. problem with I2C support and want to see more of what is going on.
  59. config I2C_DEBUG_ALGO
  60. bool "I2C Algorithm debugging messages"
  61. help
  62. Say Y here if you want the I2C algorithm drivers to produce a bunch
  63. of debug messages to the system log. Select this if you are having
  64. a problem with I2C support and want to see more of what is going
  65. on.
  66. config I2C_DEBUG_BUS
  67. bool "I2C Bus debugging messages"
  68. help
  69. Say Y here if you want the I2C bus drivers to produce a bunch of
  70. debug messages to the system log. Select this if you are having
  71. a problem with I2C support and want to see more of what is going
  72. on.
  73. config I2C_DEBUG_CHIP
  74. bool "I2C Chip debugging messages"
  75. help
  76. Say Y here if you want the I2C chip drivers to produce a bunch of
  77. debug messages to the system log. Select this if you are having
  78. a problem with I2C support and want to see more of what is going
  79. on.
  80. endif # I2C