Johannes Stezenbach writes: > What Jean writes only applies if you have a struct i2c_client > and i2c_driver to work with. the you can do lokcing in the > i2c_driver. > > But we don't, IIRC because of problems with bus probing > done yb the i2c-core. > Not having an i2c_client is also the reason why we can't > use the i2c_smbus_* functions. > > Well, maybe we could fix this and then use i2c_client > and i2c_driver everywhere, but it still wouldn't solve > the i2c-dev problem, which I2C_M_STOP would in a very > simple and elegant way. I2C_M_STOP might also be useful > to talk to devices behind a repeater/gate or hub. Another nice case is a card with 2 PLLs with identical addresses behind gates! This cannot be handled with an i2c_client anyway. Another problem with repeaters is, that some close by themselves after a STOP. So, another message getting in-between completely messes up the whole transfer. Ralph _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
