2 bool "I2C device support"
10 bool "Freescale i.MX I2C controller"
12 select I2C_QUIRK_REG if FSL_LSCH3 || SOC_LS102XA
15 bool "Enable Driver Model for I2C drivers"
18 Enable driver model for I2C. The I2C uclass interface: probe, read,
19 write and speed, is implemented with the bus drivers operations,
20 which provide methods for bus setting and data transfer. Each chip
21 device (bus child) info is kept as parent platdata. The interface
22 is defined in include/i2c.h. When i2c bus driver supports the i2c
23 uclass, but the device drivers not, then DM_I2C_COMPAT config can
24 be used as compatibility layer.
27 bool "Enable I2C compatibility layer"
30 Enable old-style I2C functions for compatibility with existing code.
31 This option can be enabled as a temporary measure to avoid needing
32 to convert all code for a board in a single commit. It should not
33 be enabled for any board in an official release.
35 config I2C_CROS_EC_TUNNEL
36 tristate "Chrome OS EC tunnel I2C bus"
39 This provides an I2C bus that will tunnel i2c commands through to
40 the other side of the Chrome OS EC to the I2C bus connected there.
41 This will work whatever the interface used to talk to the EC (SPI,
42 I2C or LPC). Some Chromebooks use this when the hardware design
43 does not allow direct access to the main PMIC from the AP.
45 config I2C_CROS_EC_LDO
46 bool "Provide access to LDOs on the Chrome OS EC"
49 On many Chromebooks the main PMIC is inaccessible to the AP. This is
50 often dealt with by using an I2C pass-through interface provided by
51 the EC. On some unfortunate models (e.g. Spring) the pass-through
52 is not available, and an LDO message is available instead. This
53 option enables a driver which provides very basic access to those
54 regulators, via the EC. We implement this as an I2C bus which
55 emulates just the TPS65090 messages we know about. This is done to
56 avoid duplicating the logic in the TPS65090 regulator driver for
57 enabling/disabling an LDO.
60 bool "Enable Driver Model for software emulated I2C bus driver"
61 depends on DM_I2C && DM_GPIO
63 Enable the i2c bus driver emulation by using the GPIOs. The bus GPIO
64 configuration is given by the device tree. Kernel-style device tree
65 bindings are supported.
66 Binding info: doc/device-tree-bindings/i2c/i2c-gpio.txt
68 config SYS_I2C_SANDBOX
69 bool "Sandbox I2C driver"
70 depends on SANDBOX && DM_I2C
72 Enable I2C support for sandbox. This is an emulation of a real I2C
73 bus. Devices can be attached to the bus using the device tree
74 which specifies the driver to use. As an example, see this device
75 tree fragment from sandbox.dts. It shows that the I2C bus has a
76 single EEPROM at address 0x2c (7-bit address) which is emulated by
77 the driver for "sandbox,i2c-eeprom", which is in
78 drivers/misc/i2c_eeprom_emul.c.
84 compatible = "sandbox,i2c";
85 clock-frequency = <400000>;
88 compatible = "i2c-eeprom";
90 compatible = "sandbox,i2c-eeprom";
91 sandbox,filename = "i2c.bin";
98 config SYS_I2C_UNIPHIER
99 bool "UniPhier I2C driver"
100 depends on ARCH_UNIPHIER && DM_I2C
103 Support for UniPhier I2C controller driver. This I2C controller
104 is used on PH1-LD4, PH1-sLD8 or older UniPhier SoCs.
106 config SYS_I2C_UNIPHIER_F
107 bool "UniPhier FIFO-builtin I2C driver"
108 depends on ARCH_UNIPHIER && DM_I2C
111 Support for UniPhier FIFO-builtin I2C controller driver.
112 This I2C controller is used on PH1-Pro4 or newer UniPhier SoCs.
114 source "drivers/i2c/muxes/Kconfig"