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