2 # I2C subsystem configuration
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.
17 Both I2C and SMBus are supported here. You will need this for
18 hardware sensors support, and also for Video For Linux support.
20 If you want I2C support, you should say Y here and also to the
21 specific driver for your bus adapter(s) below.
23 This I2C support can also be built as a module. If so, the module
24 will be called i2c-core.
26 config ACPI_I2C_OPREGION
27 bool "ACPI I2C Operation region support"
28 depends on I2C=y && ACPI
31 Say Y here if you want to enable ACPI I2C operation region support.
32 Operation Regions allow firmware (BIOS) code to access I2C slave devices,
33 such as smart batteries through an I2C host controller driver.
42 bool "Enable compatibility bits for old user-space"
45 Say Y here if you intend to run lm-sensors 3.1.1 or older, or any
46 other user-space package which expects i2c adapters to be class
47 devices. If you don't know, say Y.
50 tristate "I2C device interface"
52 Say Y here to use i2c-* device files, usually found in the /dev
53 directory on your system. They make it possible to have user-space
54 programs use the I2C bus. Information on how to do this is
55 contained in the file <file:Documentation/i2c/dev-interface>.
57 This support is also available as a module. If so, the module
58 will be called i2c-dev.
61 tristate "I2C bus multiplexing support"
64 Say Y here if you want the I2C core to support the ability to
65 handle multiplexed I2C bus topologies, by presenting each
66 multiplexed segment as a I2C adapter.
68 This support is also available as a module. If so, the module
69 will be called i2c-mux.
71 source drivers/i2c/muxes/Kconfig
73 config I2C_HELPER_AUTO
74 bool "Autoselect pertinent helper modules"
77 Some I2C bus drivers require so-called "I2C algorithm" modules
78 to work. These are basically software-only abstractions of generic
79 I2C interfaces. This option will autoselect them so that you don't
82 Unselect this only if you need to enable additional helper
83 modules, for example for use with external I2C bus drivers.
88 tristate "SMBus-specific protocols" if !I2C_HELPER_AUTO
90 Say Y here if you want support for SMBus extensions to the I2C
91 specification. At the moment, the only supported extension is
92 the SMBus alert protocol.
94 This support is also available as a module. If so, the module
95 will be called i2c-smbus.
97 source drivers/i2c/algos/Kconfig
98 source drivers/i2c/busses/Kconfig
101 tristate "I2C/SMBus Test Stub"
105 This module may be useful to developers of SMBus client drivers,
106 especially for certain kinds of sensor chips.
108 If you do build this module, be sure to read the notes and warnings
109 in <file:Documentation/i2c/i2c-stub>.
111 If you don't know what to do here, definitely say N.
114 bool "I2C slave support"
118 config I2C_SLAVE_EEPROM
119 tristate "I2C eeprom slave driver"
123 config I2C_DEBUG_CORE
124 bool "I2C Core debugging messages"
126 Say Y here if you want the I2C core to produce a bunch of debug
127 messages to the system log. Select this if you are having a
128 problem with I2C support and want to see more of what is going on.
130 config I2C_DEBUG_ALGO
131 bool "I2C Algorithm debugging messages"
133 Say Y here if you want the I2C algorithm drivers to produce a bunch
134 of debug messages to the system log. Select this if you are having
135 a problem with I2C support and want to see more of what is going
139 bool "I2C Bus debugging messages"
142 Say Y here if you want the I2C bus drivers to produce a bunch of
143 debug messages to the system log. Select this if you are having
144 a problem with I2C support and want to see more of what is going