Kconfig 1.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546
  1. config I2C_MUX
  2. bool "Support I2C multiplexers"
  3. depends on DM_I2C
  4. help
  5. This enables I2C buses to be multiplexed, so that you can select
  6. one of several buses using some sort of control mechanism. The
  7. bus select is handled automatically when that bus is accessed,
  8. using a suitable I2C MUX driver.
  9. config SPL_I2C_MUX
  10. bool "Support I2C multiplexers on SPL"
  11. depends on I2C_MUX
  12. help
  13. This enables I2C buses to be multiplexed, so that you can select
  14. one of several buses using some sort of control mechanism. The
  15. bus select is handled automatically when that bus is accessed,
  16. using a suitable I2C MUX driver.
  17. config I2C_ARB_GPIO_CHALLENGE
  18. bool "GPIO-based I2C arbitration"
  19. depends on I2C_MUX
  20. help
  21. If you say yes to this option, support will be included for an
  22. I2C multimaster arbitration scheme using GPIOs and a challenge &
  23. response mechanism where masters have to claim the bus by asserting
  24. a GPIO.
  25. config I2C_MUX_PCA954x
  26. tristate "TI PCA954x I2C Mux/switches"
  27. depends on I2C_MUX
  28. help
  29. If you say yes here you get support for the TI PCA954x I2C mux/switch
  30. devices. It is x width I2C multiplexer which enables to partitioning
  31. I2C bus and connect multiple devices with the same address to the same
  32. I2C controller where driver handles proper routing to target i2c
  33. device. Supported chips are PCA9543, PCA9544, PCA9546, PCA9547,
  34. PCA9548 and PCA9646.
  35. config I2C_MUX_GPIO
  36. tristate "GPIO-based I2C multiplexer"
  37. depends on I2C_MUX && DM_GPIO
  38. help
  39. If you say yes to this option, support will be included for
  40. a GPIO based I2C multiplexer. This driver provides access to
  41. I2C busses connected through a MUX, which is controlled
  42. through GPIO pins.