avionic design with actual uboot and tooling
submodule of avionic design uboot bootloader and with included tools to get you started , read readme.md and readme-tk1-loader.md
This commit is contained in:
36
u-boot/drivers/i2c/muxes/Kconfig
Normal file
36
u-boot/drivers/i2c/muxes/Kconfig
Normal file
@@ -0,0 +1,36 @@
|
||||
config I2C_MUX
|
||||
bool "Support I2C multiplexers"
|
||||
depends on DM_I2C
|
||||
help
|
||||
This enables I2C buses to be multiplexed, so that you can select
|
||||
one of several buses using some sort of control mechanism. The
|
||||
bus select is handled automatically when that bus is accessed,
|
||||
using a suitable I2C MUX driver.
|
||||
|
||||
config SPL_I2C_MUX
|
||||
bool "Support I2C multiplexers on SPL"
|
||||
depends on I2C_MUX
|
||||
help
|
||||
This enables I2C buses to be multiplexed, so that you can select
|
||||
one of several buses using some sort of control mechanism. The
|
||||
bus select is handled automatically when that bus is accessed,
|
||||
using a suitable I2C MUX driver.
|
||||
|
||||
config I2C_ARB_GPIO_CHALLENGE
|
||||
bool "GPIO-based I2C arbitration"
|
||||
depends on I2C_MUX
|
||||
help
|
||||
If you say yes to this option, support will be included for an
|
||||
I2C multimaster arbitration scheme using GPIOs and a challenge &
|
||||
response mechanism where masters have to claim the bus by asserting
|
||||
a GPIO.
|
||||
|
||||
config I2C_MUX_PCA954x
|
||||
tristate "TI PCA954x I2C Mux/switches"
|
||||
depends on I2C_MUX
|
||||
help
|
||||
If you say yes here you get support for the TI PCA954x
|
||||
I2C mux/switch devices. It is x width I2C multiplexer which enables to
|
||||
paritioning I2C bus and connect multiple devices with the same address
|
||||
to the same I2C controller where driver handles proper routing to
|
||||
target i2c device. PCA9544 and PCA9548 are supported.
|
||||
Reference in New Issue
Block a user