>>>>> "Jean" == Jean Delvare <khali@xxxxxxxxxxxx> writes: >> True. I unsually solve this by making sure the multiplexer starts in >> an unconnected state so the trunk probe doesn't find anything, or >> simply not use the old style probing. Jean> Please keep in mind that the difficulty here is with probing itself, Jean> not just with old-style. The new binding model also has a detection Jean> mode, which is also affected. Making sure that the multiplexer is in an Jean> unconnected state initially isn't sufficient, as you can load I2C chip Jean> drivers at any later point in time and this will trigger a new Jean> detection cycle. And not all multiplexers can be disabled that way, Jean> some have always one outer channel enabled. Yes, but my code (http://www.mail-archive.com/i2c@xxxxxxxxxxxxxx/msg01539.html) does: lock parent mutex enable mux do transfer on parent bus disable mux unlock parent So that afaik shouldn't be a problem. If your mux doesn't have an enable control and there's no unused connection you can use instead, then that ofcourse doesn't work. -- Bye, Peter Korsgaard -- 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
