]>
Commit | Line | Data |
---|---|---|
7f528135 ML |
1 | # |
2 | # Multiplexer I2C chip drivers configuration | |
3 | # | |
4 | ||
5 | menu "Multiplexer I2C Chip support" | |
6 | depends on I2C_MUX | |
7 | ||
b81dfaa0 DA |
8 | config I2C_ARB_GPIO_CHALLENGE |
9 | tristate "GPIO-based I2C arbitration" | |
7e5cd69a GU |
10 | depends on GPIOLIB || COMPILE_TEST |
11 | depends on OF | |
b81dfaa0 DA |
12 | help |
13 | If you say yes to this option, support will be included for an | |
14 | I2C multimaster arbitration scheme using GPIOs and a challenge & | |
15 | response mechanism where masters have to claim the bus by asserting | |
16 | a GPIO. | |
17 | ||
18 | This driver can also be built as a module. If so, the module | |
19 | will be called i2c-arb-gpio-challenge. | |
20 | ||
92ed1a76 PK |
21 | config I2C_MUX_GPIO |
22 | tristate "GPIO-based I2C multiplexer" | |
76ec9d18 | 23 | depends on GPIOLIB |
92ed1a76 PK |
24 | help |
25 | If you say yes to this option, support will be included for a | |
26 | GPIO based I2C multiplexer. This driver provides access to | |
27 | I2C busses connected through a MUX, which is controlled | |
28 | through GPIO pins. | |
29 | ||
30 | This driver can also be built as a module. If so, the module | |
e7065e20 | 31 | will be called i2c-mux-gpio. |
92ed1a76 | 32 | |
ac8498f0 PR |
33 | config I2C_MUX_GPMUX |
34 | tristate "General Purpose I2C multiplexer" | |
35 | select MULTIPLEXER | |
36 | depends on OF || COMPILE_TEST | |
37 | help | |
38 | If you say yes to this option, support will be included for a | |
39 | general purpose I2C multiplexer. This driver provides access to | |
40 | I2C busses connected through a MUX, which in turn is controlled | |
41 | by a MUX-controller from the MUX subsystem. | |
42 | ||
43 | This driver can also be built as a module. If so, the module | |
44 | will be called i2c-mux-gpmux. | |
45 | ||
dbed8a80 MH |
46 | config I2C_MUX_LTC4306 |
47 | tristate "LTC LTC4306/5 I2C multiplexer" | |
48 | select GPIOLIB | |
49 | select REGMAP_I2C | |
50 | help | |
51 | If you say yes here you get support for the Analog Devices | |
52 | LTC4306 or LTC4305 I2C mux/switch devices. | |
53 | ||
54 | This driver can also be built as a module. If so, the module | |
55 | will be called i2c-mux-ltc4306. | |
56 | ||
ae63b13b GR |
57 | config I2C_MUX_PCA9541 |
58 | tristate "NXP PCA9541 I2C Master Selector" | |
ae63b13b GR |
59 | help |
60 | If you say yes here you get support for the NXP PCA9541 | |
61 | I2C Master Selector. | |
62 | ||
63 | This driver can also be built as a module. If so, the module | |
b4f0b74e | 64 | will be called i2c-mux-pca9541. |
ae63b13b | 65 | |
7f528135 ML |
66 | config I2C_MUX_PCA954x |
67 | tristate "Philips PCA954x I2C Mux/switches" | |
7e5cd69a | 68 | depends on GPIOLIB || COMPILE_TEST |
7f528135 ML |
69 | help |
70 | If you say yes here you get support for the Philips PCA954x | |
71 | I2C mux/switch devices. | |
72 | ||
73 | This driver can also be built as a module. If so, the module | |
b4f0b74e | 74 | will be called i2c-mux-pca954x. |
7f528135 | 75 | |
ae58d1e4 SW |
76 | config I2C_MUX_PINCTRL |
77 | tristate "pinctrl-based I2C multiplexer" | |
78 | depends on PINCTRL | |
79 | help | |
80 | If you say yes to this option, support will be included for an I2C | |
81 | multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing. | |
82 | This is useful for SoCs whose I2C module's signals can be routed to | |
83 | different sets of pins at run-time. | |
84 | ||
85 | This driver can also be built as a module. If so, the module will be | |
d1510a2e | 86 | called i2c-mux-pinctrl. |
ae58d1e4 | 87 | |
b3fdd327 YS |
88 | config I2C_MUX_REG |
89 | tristate "Register-based I2C multiplexer" | |
93d710a6 | 90 | depends on HAS_IOMEM |
b3fdd327 YS |
91 | help |
92 | If you say yes to this option, support will be included for a | |
93 | register based I2C multiplexer. This driver provides access to | |
94 | I2C busses connected through a MUX, which is controlled | |
95 | by a single register. | |
96 | ||
97 | This driver can also be built as a module. If so, the module | |
98 | will be called i2c-mux-reg. | |
99 | ||
50a5ba87 WS |
100 | config I2C_DEMUX_PINCTRL |
101 | tristate "pinctrl-based I2C demultiplexer" | |
102 | depends on PINCTRL && OF | |
103 | select OF_DYNAMIC | |
104 | help | |
105 | If you say yes to this option, support will be included for an I2C | |
106 | demultiplexer that uses the pinctrl subsystem. This is useful if you | |
107 | want to change the I2C master at run-time depending on features. | |
108 | ||
c02b7bf5 VP |
109 | config I2C_MUX_MLXCPLD |
110 | tristate "Mellanox CPLD based I2C multiplexer" | |
111 | help | |
112 | If you say yes to this option, support will be included for a | |
113 | CPLD based I2C multiplexer. This driver provides access to | |
114 | I2C busses connected through a MUX, which is controlled | |
115 | by a CPLD register. | |
116 | ||
117 | This driver can also be built as a module. If so, the module | |
118 | will be called i2c-mux-mlxcpld. | |
119 | ||
7f528135 | 120 | endmenu |