1# 2# I2C subsystem configuration 3# 4 5menu "I2C support" 6 7config DM_I2C 8 bool "Enable Driver Model for I2C drivers" 9 depends on DM 10 help 11 Enable driver model for I2C. The I2C uclass interface: probe, read, 12 write and speed, is implemented with the bus drivers operations, 13 which provide methods for bus setting and data transfer. Each chip 14 device (bus child) info is kept as parent platdata. The interface 15 is defined in include/i2c.h. When i2c bus driver supports the i2c 16 uclass, but the device drivers not, then DM_I2C_COMPAT config can 17 be used as compatibility layer. 18 19config DM_I2C_COMPAT 20 bool "Enable I2C compatibility layer" 21 depends on DM 22 help 23 Enable old-style I2C functions for compatibility with existing code. 24 This option can be enabled as a temporary measure to avoid needing 25 to convert all code for a board in a single commit. It should not 26 be enabled for any board in an official release. 27 28config I2C_CROS_EC_TUNNEL 29 tristate "Chrome OS EC tunnel I2C bus" 30 depends on CROS_EC 31 help 32 This provides an I2C bus that will tunnel i2c commands through to 33 the other side of the Chrome OS EC to the I2C bus connected there. 34 This will work whatever the interface used to talk to the EC (SPI, 35 I2C or LPC). Some Chromebooks use this when the hardware design 36 does not allow direct access to the main PMIC from the AP. 37 38config I2C_CROS_EC_LDO 39 bool "Provide access to LDOs on the Chrome OS EC" 40 depends on CROS_EC 41 ---help--- 42 On many Chromebooks the main PMIC is inaccessible to the AP. This is 43 often dealt with by using an I2C pass-through interface provided by 44 the EC. On some unfortunate models (e.g. Spring) the pass-through 45 is not available, and an LDO message is available instead. This 46 option enables a driver which provides very basic access to those 47 regulators, via the EC. We implement this as an I2C bus which 48 emulates just the TPS65090 messages we know about. This is done to 49 avoid duplicating the logic in the TPS65090 regulator driver for 50 enabling/disabling an LDO. 51 52config DM_I2C_GPIO 53 bool "Enable Driver Model for software emulated I2C bus driver" 54 depends on DM_I2C && DM_GPIO 55 help 56 Enable the i2c bus driver emulation by using the GPIOs. The bus GPIO 57 configuration is given by the device tree. Kernel-style device tree 58 bindings are supported. 59 Binding info: doc/device-tree-bindings/i2c/i2c-gpio.txt 60 61config SYS_I2C_INTEL 62 bool "Intel I2C/SMBUS driver" 63 depends on DM_I2C 64 help 65 Add support for the Intel SMBUS driver. So far this driver is just 66 a stub which perhaps some basic init. There is no implementation of 67 the I2C API meaning that any I2C operations will immediately fail 68 for now. 69 70config SYS_I2C_ROCKCHIP 71 bool "Rockchip I2C driver" 72 depends on DM_I2C 73 help 74 Add support for the Rockchip I2C driver. This is used with various 75 Rockchip parts such as RK3126, RK3128, RK3036 and RK3288. All chips 76 have several I2C ports and all are provided, controled by the 77 device tree. 78 79config SYS_I2C_SANDBOX 80 bool "Sandbox I2C driver" 81 depends on SANDBOX && DM_I2C 82 help 83 Enable I2C support for sandbox. This is an emulation of a real I2C 84 bus. Devices can be attached to the bus using the device tree 85 which specifies the driver to use. As an example, see this device 86 tree fragment from sandbox.dts. It shows that the I2C bus has a 87 single EEPROM at address 0x2c (7-bit address) which is emulated by 88 the driver for "sandbox,i2c-eeprom", which is in 89 drivers/misc/i2c_eeprom_emul.c. 90 91 i2c@0 { 92 #address-cells = <1>; 93 #size-cells = <0>; 94 reg = <0>; 95 compatible = "sandbox,i2c"; 96 clock-frequency = <400000>; 97 eeprom@2c { 98 reg = <0x2c>; 99 compatible = "i2c-eeprom"; 100 emul { 101 compatible = "sandbox,i2c-eeprom"; 102 sandbox,filename = "i2c.bin"; 103 sandbox,size = <128>; 104 }; 105 }; 106 }; 107 108 109config SYS_I2C_UNIPHIER 110 bool "UniPhier I2C driver" 111 depends on ARCH_UNIPHIER && DM_I2C 112 default y 113 help 114 Support for UniPhier I2C controller driver. This I2C controller 115 is used on PH1-LD4, PH1-sLD8 or older UniPhier SoCs. 116 117config SYS_I2C_UNIPHIER_F 118 bool "UniPhier FIFO-builtin I2C driver" 119 depends on ARCH_UNIPHIER && DM_I2C 120 default y 121 help 122 Support for UniPhier FIFO-builtin I2C controller driver. 123 This I2C controller is used on PH1-Pro4 or newer UniPhier SoCs. 124 125source "drivers/i2c/muxes/Kconfig" 126 127endmenu 128