Kconfig 2.3 KB

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