]> git.ipfire.org Git - people/ms/u-boot.git/blame - drivers/i2c/Kconfig
dm: fsl_i2c: Enable DM for FSL I2C
[people/ms/u-boot.git] / drivers / i2c / Kconfig
CommitLineData
0b11dbf7
MY
1#
2# I2C subsystem configuration
3#
4
5menu "I2C support"
6
b6036bcd
MY
7config DM_I2C
8 bool "Enable Driver Model for I2C drivers"
9 depends on DM
10 help
705fcf4d
PM
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.
26f820f3 18
4bba9d3f
SG
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
cc456bd7
SG
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
f48eaf01
SG
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.
cc456bd7 51
c54473cb
PM
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
dbc82ce3 61config SYS_I2C_FSL
62 bool "Freescale I2C bus driver"
63 depends on DM_I2C
64 help
65 Add support for Freescale I2C busses as used on MPC8240, MPC8245, and
66 MPC85xx processors.
67
fdec2d21
MF
68config SYS_I2C_CADENCE
69 tristate "Cadence I2C Controller"
70 depends on DM_I2C && (ARCH_ZYNQ || ARM64)
71 help
72 Say yes here to select Cadence I2C Host Controller. This controller is
73 e.g. used by Xilinx Zynq.
74
abb0b01e
SG
75config SYS_I2C_INTEL
76 bool "Intel I2C/SMBUS driver"
77 depends on DM_I2C
78 help
79 Add support for the Intel SMBUS driver. So far this driver is just
80 a stub which perhaps some basic init. There is no implementation of
81 the I2C API meaning that any I2C operations will immediately fail
82 for now.
83
34374699
SG
84config SYS_I2C_ROCKCHIP
85 bool "Rockchip I2C driver"
86 depends on DM_I2C
87 help
88 Add support for the Rockchip I2C driver. This is used with various
89 Rockchip parts such as RK3126, RK3128, RK3036 and RK3288. All chips
90 have several I2C ports and all are provided, controled by the
91 device tree.
92
1174aada
SG
93config SYS_I2C_SANDBOX
94 bool "Sandbox I2C driver"
95 depends on SANDBOX && DM_I2C
96 help
97 Enable I2C support for sandbox. This is an emulation of a real I2C
98 bus. Devices can be attached to the bus using the device tree
99 which specifies the driver to use. As an example, see this device
100 tree fragment from sandbox.dts. It shows that the I2C bus has a
101 single EEPROM at address 0x2c (7-bit address) which is emulated by
102 the driver for "sandbox,i2c-eeprom", which is in
103 drivers/misc/i2c_eeprom_emul.c.
104
105 i2c@0 {
106 #address-cells = <1>;
107 #size-cells = <0>;
108 reg = <0>;
109 compatible = "sandbox,i2c";
110 clock-frequency = <400000>;
111 eeprom@2c {
112 reg = <0x2c>;
113 compatible = "i2c-eeprom";
114 emul {
115 compatible = "sandbox,i2c-eeprom";
116 sandbox,filename = "i2c.bin";
117 sandbox,size = <128>;
118 };
119 };
120 };
121
122
26f820f3
MY
123config SYS_I2C_UNIPHIER
124 bool "UniPhier I2C driver"
125 depends on ARCH_UNIPHIER && DM_I2C
126 default y
127 help
b6ef3a3f
MY
128 Support for UniPhier I2C controller driver. This I2C controller
129 is used on PH1-LD4, PH1-sLD8 or older UniPhier SoCs.
238bd0b8
MY
130
131config SYS_I2C_UNIPHIER_F
132 bool "UniPhier FIFO-builtin I2C driver"
133 depends on ARCH_UNIPHIER && DM_I2C
134 default y
135 help
b6ef3a3f 136 Support for UniPhier FIFO-builtin I2C controller driver.
238bd0b8 137 This I2C controller is used on PH1-Pro4 or newer UniPhier SoCs.
3d1957f0
SG
138
139source "drivers/i2c/muxes/Kconfig"
0b11dbf7
MY
140
141endmenu