Re: Again on virtual i2c adapter support.

[Peter Korsgaard <jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>]

>>>>> "Jean" == Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org> 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-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org/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