On 2016-08-21 20:32, Jonathan Cameron wrote: > On 15/08/16 19:38, Linus Walleij wrote: >> Since the MPU-3050 has an outgoing I2C port it needs to act as >> an I2C mux. This means that the device is switching I2C traffic >> to devices beyond it. On my system this is the only way to reach >> the accelerometer. The "sensor fusion" ability of the MPU-3050 >> to directly talk to the device on the outgoing I2C port is >> currently not used by the driver, but it has code to allow I2C >> traffic to pass through so that the Linux kernel can reach the >> device on the other side with a kernel driver. > Cc'd Peter Rosin as he's maintaining the i2c mux code now. The i2c-mux handling looks sane, with the current code, but I had an update in mind for the next merge window that affects this: [PATCH v2 0/8] devicetree cleanup for i2c muxes/arbs/gates https://lkml.org/lkml/2016/8/15/569 Specifically patch 3/8 is relevant [PATCH v2 3/8] dt-bindings: i2c: add support for 'i2c-gate' subnode https://lkml.org/lkml/2016/8/15/270 (implemented in 5/7) The above is not in next (yet). I don't know how this situation is best handled? Cheers, Peter -- To unsubscribe from this list: send the line "unsubscribe linux-iio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
