On Wed, Feb 13, 2013 at 10:45 AM, Olof Johansson <olof@xxxxxxxxx> wrote: >> + i2c-parent = <&{/i2c@12CA0000}>; > > Why use this custom i2c-parent property? The arbitrator should just be > under the i2c controller in the device tree, and thus parent would be > derived from the topology there. Ah. Reading up on the discussions for the other mux bindings, there's the issue of the arbitrator not being addressable/accessible via i2c. Sigh, awkward and annoying, since it breaks the topography for the hardware apart due to the arbitrator. But I guess there's no good alternative. :( -Olof -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html