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