drivers/i2c/muxes/Kconfig

   1 #
   2 # Multiplexer I2C chip drivers configuration
   3 #
   4
   5 menu "Multiplexer I2C Chip support"
   6         depends on I2C_MUX
   7
   8 config 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
  20 config I2C_MUX_PCA9541
  21         tristate "NXP PCA9541 I2C Master Selector"
  22         depends on EXPERIMENTAL
  23         help
  24           If you say yes here you get support for the NXP PCA9541
  25           I2C Master Selector.
  26
  27           This driver can also be built as a module.  If so, the module
  28           will be called i2c-mux-pca9541.
  29
  30 config I2C_MUX_PCA954x
  31         tristate "Philips PCA954x I2C Mux/switches"
  32         depends on EXPERIMENTAL
  33         help
  34           If you say yes here you get support for the Philips PCA954x
  35           I2C mux/switch devices.
  36
  37           This driver can also be built as a module.  If so, the module
  38           will be called i2c-mux-pca954x.
  39
  40 config I2C_MUX_PINCTRL
  41         tristate "pinctrl-based I2C multiplexer"
  42         depends on PINCTRL
  43         help
  44           If you say yes to this option, support will be included for an I2C
  45           multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
  46           This is useful for SoCs whose I2C module's signals can be routed to
  47           different sets of pins at run-time.
  48
  49           This driver can also be built as a module. If so, the module will be
  50           called pinctrl-i2cmux.
  51
  52 endmenu