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_ARB_GPIO_CHALLENGE
   9         tristate "GPIO-based I2C arbitration"
  10         depends on GPIOLIB && OF
  11         help
  12           If you say yes to this option, support will be included for an
  13           I2C multimaster arbitration scheme using GPIOs and a challenge &
  14           response mechanism where masters have to claim the bus by asserting
  15           a GPIO.
  16
  17           This driver can also be built as a module.  If so, the module
  18           will be called i2c-arb-gpio-challenge.
  19
  20 config I2C_MUX_GPIO
  21         tristate "GPIO-based I2C multiplexer"
  22         depends on GPIOLIB
  23         help
  24           If you say yes to this option, support will be included for a
  25           GPIO based I2C multiplexer. This driver provides access to
  26           I2C busses connected through a MUX, which is controlled
  27           through GPIO pins.
  28
  29           This driver can also be built as a module.  If so, the module
  30           will be called i2c-mux-gpio.
  31
  32 config I2C_MUX_PCA9541
  33         tristate "NXP PCA9541 I2C Master Selector"
  34         help
  35           If you say yes here you get support for the NXP PCA9541
  36           I2C Master Selector.
  37
  38           This driver can also be built as a module.  If so, the module
  39           will be called i2c-mux-pca9541.
  40
  41 config I2C_MUX_PCA954x
  42         tristate "Philips PCA954x I2C Mux/switches"
  43         depends on GPIOLIB
  44         help
  45           If you say yes here you get support for the Philips PCA954x
  46           I2C mux/switch devices.
  47
  48           This driver can also be built as a module.  If so, the module
  49           will be called i2c-mux-pca954x.
  50
  51 config I2C_MUX_PINCTRL
  52         tristate "pinctrl-based I2C multiplexer"
  53         depends on PINCTRL
  54         help
  55           If you say yes to this option, support will be included for an I2C
  56           multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
  57           This is useful for SoCs whose I2C module's signals can be routed to
  58           different sets of pins at run-time.
  59
  60           This driver can also be built as a module. If so, the module will be
  61           called pinctrl-i2cmux.
  62
  63 endmenu