On Sun, 17 Nov 2013 09:23:32 -0800, Guenter Roeck wrote: > I think it would still be unique name, as long as the parent adapter number > is well defined (which it hopefully is). At least with the change I can > 1) identify the mux and 2) walk back in the tree of i2c adapters to find > the root. Using above example, I know that i2c-2-mux (chan_id 0) is on bus 2. > Bus 2 is i2c-0-mux (chan_id 0), so I know it is connected to bus 0. > > Am I missing something ? You're not missing anything. It is indeed possible to "resolve" the name to uniqueness. My only concern is that someone has to do it, and for example libsensors currently doesn't. The configuration file parser would have to be extended to do that resolution in order to fully support chip-instance-specific configuration statements on multiplexed topologies. Same goes for i2c-tools: normally you can pass the bus by name instead of number, but with the need to resolve the name of muxed branches, this no longer works. I'm not saying this is a blocker problem, just something to keep in mind. -- 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
