Hi Peter, On Fri, 23 Jan 2009 10:23:05 +0100, Peter Korsgaard wrote: > >>>>> "Jean" == Jean Delvare <khali@xxxxxxxxxxxx> writes: > > Hi, > > Jean> Oh, and please stop calling the thing "virtual i2c adapter support". > Jean> These adapters are very real. What you are working on is better > Jean> described as "i2c bus multiplexing support". > > Not only that, it's afaik about doing i2c bus multiplexing where the > multiplexers are themselves i2c devices - E.G. stuff where you might > need to recursively call into the i2c core. > > I have been doing i2c multiplexers where the multiplexers themselves > are not controlled through i2c for years without problems. > > I afaik even posted an example driver back when Dave posted his > multiplex hack. There are still a few caveats when doing this. In particular, if you use drivers which probe the I2C bus for devices, you must make sure that the devices will be properly found on either the trunk or one of the multiplexer branches but not both. In fact this is with this specific case in mind that I decided to wait for the i2c device driver binding model to be cleaned up before going on with full multiplexing support. That being said, yes, you're correct, multiplexing where the multiplexer chip isn't on the bus itself is a lot easier and can already be done today in some cases. -- Jean Delvare -- 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
