xref: /openbmc/linux/drivers/i2c/muxes/Kconfig (revision 97da55fc)
1#
2# Multiplexer I2C chip drivers configuration
3#
4
5menu "Multiplexer I2C Chip support"
6	depends on I2C_MUX
7
8config I2C_MUX_GPIO
9	tristate "GPIO-based I2C multiplexer"
10	depends on GENERIC_GPIO
11	help
12	  If you say yes to this option, support will be included for a
13	  GPIO based I2C multiplexer. This driver provides access to
14	  I2C busses connected through a MUX, which is controlled
15	  through GPIO pins.
16
17	  This driver can also be built as a module.  If so, the module
18	  will be called i2c-mux-gpio.
19
20config I2C_MUX_PCA9541
21	tristate "NXP PCA9541 I2C Master Selector"
22	help
23	  If you say yes here you get support for the NXP PCA9541
24	  I2C Master Selector.
25
26	  This driver can also be built as a module.  If so, the module
27	  will be called i2c-mux-pca9541.
28
29config I2C_MUX_PCA954x
30	tristate "Philips PCA954x I2C Mux/switches"
31	help
32	  If you say yes here you get support for the Philips PCA954x
33	  I2C mux/switch devices.
34
35	  This driver can also be built as a module.  If so, the module
36	  will be called i2c-mux-pca954x.
37
38config I2C_MUX_PINCTRL
39	tristate "pinctrl-based I2C multiplexer"
40	depends on PINCTRL
41	help
42	  If you say yes to this option, support will be included for an I2C
43	  multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
44	  This is useful for SoCs whose I2C module's signals can be routed to
45	  different sets of pins at run-time.
46
47	  This driver can also be built as a module. If so, the module will be
48	  called pinctrl-i2cmux.
49
50endmenu
51