Hi all, On 6/17/24 14:08, Bastien Curutchet wrote:
Hi all, The i2c-gpio-mux can be used to describe a multiplexer built upon several i2c isolators having an enable pin (such as LTC4310): +---------------+ +------+ +------+ | +-----------+ | | dev | | dev | | | GPIO_EN_A |-|-----------| +------+ +------+ | +-----------+ | +-----+---+ | | | | |--| isol. A |---------+---------+ | +-----+ | | +---------+ | SOC | I2C |---|--| | +-----+ | | +---------+ | | |--| isol. B |------+---------+---------+ | +-----------+ | +-----+---+ | | | | | GPIO_EN_B |-|-----------| +------+ +------+ +------+ | +-----------+ | | dev | | dev | | dev | +---------------+ +------+ +------+ +------+ These isolators often need some time between their enable pin's assertion and the first i2c transfer. If the first i2c transfer happens before this enabling time is reached, transfer fails. There is no available option to configure such a time in the i2c-gpio-mux driver. Add a optional property in the bindings called 'transition-delay-us'. If present, driver waits for this delay every time a new bus is selected, i.e. before returning from the bus_select() callback. Changes in v2: * Rewrite bindings' commit log * Express the 'transition delay' in us instead of ms Changes in v3: * Rename DT property to 'settle-time-us' * Use fsleep instead of udelay [v1] : https://lore.kernel.org/all/20240527113908.127893-1-bastien.curutchet@xxxxxxxxxxx/ [v2] : https://lore.kernel.org/all/20240529091739.10808-1-bastien.curutchet@xxxxxxxxxxx/
I don't think I've received any feedback since the bindings were reviewed by Krzysztof. Has anyone had a chance to look at this V3 iteration yet?
Best regards, Bastien
