Kconfig 1.5 KB

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