Lines Matching +full:i2c +full:- +full:bus
1 # SPDX-License-Identifier: GPL-2.0-only
3 # I2C subsystem configuration
6 menu "I2C support"
8 config I2C config
9 tristate "I2C support"
13 I2C (pronounce: I-squared-C) is a slow serial bus protocol used in
15 or System Management Bus is a subset of the I2C protocol. More
16 information is contained in the directory <file:Documentation/i2c/>,
19 Both I2C and SMBus are supported here. You will need this for
22 If you want I2C support, you should say Y here and also to the
23 specific driver for your bus adapter(s) below.
25 This I2C support can also be built as a module. If so, the module
26 will be called i2c-core.
29 bool "ACPI I2C Operation region support"
30 depends on I2C=y && ACPI
33 Say Y here if you want to enable ACPI I2C operation region support.
34 Operation Regions allow firmware (BIOS) code to access I2C slave devices,
35 such as smart batteries through an I2C host controller driver.
37 if I2C
44 tristate "I2C device interface"
46 Say Y here to use i2c-* device files, usually found in the /dev
47 directory on your system. They make it possible to have user-space
48 programs use the I2C bus. Information on how to do this is
49 contained in the file <file:Documentation/i2c/dev-interface.rst>.
52 will be called i2c-dev.
55 tristate "I2C bus multiplexing support"
57 Say Y here if you want the I2C core to support the ability to
58 handle multiplexed I2C bus topologies, by presenting each
59 multiplexed segment as a I2C adapter.
62 will be called i2c-mux.
64 source "drivers/i2c/muxes/Kconfig"
67 tristate "I2C Address Translator (ATR) support" if COMPILE_TEST
69 Enable support for I2C Address Translator (ATR) chips.
71 An ATR allows accessing multiple I2C busses from a single
72 physical bus via address translation instead of bus selection as
73 i2c-muxes do.
79 Some I2C bus drivers require so-called "I2C algorithm" modules
80 to work. These are basically software-only abstractions of generic
81 I2C interfaces. This option will autoselect them so that you don't
85 modules, for example for use with external I2C bus drivers.
90 tristate "SMBus-specific protocols" if !I2C_HELPER_AUTO
92 Say Y here if you want support for SMBus extensions to the I2C
97 will be called i2c-smbus.
99 source "drivers/i2c/algos/Kconfig"
100 source "drivers/i2c/busses/Kconfig"
103 tristate "I2C/SMBus Test Stub"
110 in <file:Documentation/i2c/i2c-stub.rst>.
115 bool "I2C slave support"
117 This enables Linux to act as an I2C slave device. Note that your I2C
118 bus master driver also needs to support this functionality. Please
119 read Documentation/i2c/slave-interface.rst for further details.
124 tristate "I2C eeprom slave driver"
126 This backend makes Linux behave like an I2C EEPROM. Please read
127 Documentation/i2c/slave-eeprom-backend.rst for further details.
130 tristate "I2C testunit driver"
132 This backend can be used to trigger test cases for I2C bus masters
134 multi-master, SMBus Host Notify, etc. Please read
135 Documentation/i2c/slave-testunit-backend.rst for further details.
140 bool "I2C Core debugging messages"
142 Say Y here if you want the I2C core to produce a bunch of debug
144 problem with I2C support and want to see more of what is going on.
147 bool "I2C Algorithm debugging messages"
149 Say Y here if you want the I2C algorithm drivers to produce a bunch
151 a problem with I2C support and want to see more of what is going
155 bool "I2C Bus debugging messages"
158 Say Y here if you want the I2C bus drivers to produce a bunch of
160 a problem with I2C support and want to see more of what is going
163 endif # I2C