Add the rt linux 4.1.3-rt3 as base

[kvmfornfv.git] / kernel / drivers / i2c / muxes / Kconfig

diff --git a/kernel/drivers/i2c/muxes/Kconfig b/kernel/drivers/i2c/muxes/Kconfig
new file mode 100644 (file)
index 0000000..f6d313e
--- /dev/null
+++ b/kernel/drivers/i2c/muxes/Kconfig
@@ -0,0 +1,63 @@
+#
+# Multiplexer I2C chip drivers configuration
+#
+
+menu "Multiplexer I2C Chip support"
+       depends on I2C_MUX
+
+config I2C_ARB_GPIO_CHALLENGE
+       tristate "GPIO-based I2C arbitration"
+       depends on GPIOLIB && OF
+       help
+         If you say yes to this option, support will be included for an
+         I2C multimaster arbitration scheme using GPIOs and a challenge &
+         response mechanism where masters have to claim the bus by asserting
+         a GPIO.
+
+         This driver can also be built as a module.  If so, the module
+         will be called i2c-arb-gpio-challenge.
+
+config I2C_MUX_GPIO
+       tristate "GPIO-based I2C multiplexer"
+       depends on GPIOLIB
+       help
+         If you say yes to this option, support will be included for a
+         GPIO based I2C multiplexer. This driver provides access to
+         I2C busses connected through a MUX, which is controlled
+         through GPIO pins.
+
+         This driver can also be built as a module.  If so, the module
+         will be called i2c-mux-gpio.
+
+config I2C_MUX_PCA9541
+       tristate "NXP PCA9541 I2C Master Selector"
+       help
+         If you say yes here you get support for the NXP PCA9541
+         I2C Master Selector.
+
+         This driver can also be built as a module.  If so, the module
+         will be called i2c-mux-pca9541.
+
+config I2C_MUX_PCA954x
+       tristate "Philips PCA954x I2C Mux/switches"
+       depends on GPIOLIB
+       help
+         If you say yes here you get support for the Philips PCA954x
+         I2C mux/switch devices.
+
+         This driver can also be built as a module.  If so, the module
+         will be called i2c-mux-pca954x.
+
+config I2C_MUX_PINCTRL
+       tristate "pinctrl-based I2C multiplexer"
+       depends on PINCTRL
+       help
+         If you say yes to this option, support will be included for an I2C
+         multiplexer that uses the pinctrl subsystem, i.e. pin multiplexing.
+         This is useful for SoCs whose I2C module's signals can be routed to
+         different sets of pins at run-time.
+
+         This driver can also be built as a module. If so, the module will be
+         called pinctrl-i2cmux.
+
+endmenu