Wolfram, I bumped into an issue where I needed to rely on the retry mechanism. I have a master controller and some muxed busses. However when testing I observed that the retry worked when using the bus attached to the master controller directly used the retry count set but the same behavior failed on the muxed bus since the retry count there was zero. The root cause was in the creationg of the muxed busses which have their own struct i2c_adapter which gets kzalloc in i2c_add_mux_adapter(), my (trivial) patch to this problem is to also copy the retries field of the parent to the i2c_adapter of the muxed bus. (Obviously the retry count could be set by the I2C_RETRIES ioctl, but I'd still think it's sensible to have a system initialized in a sane state). my 2 cents E. Elie De Brauwer (1): i2c-mux: Inherit retry count from parent controller for muxed bus. drivers/i2c/i2c-mux.c | 1 + 1 file changed, 1 insertion(+) -- 1.7.10.4 -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
