On Sat, Sep 3, 2016 at 6:30 PM, Jonathan Cameron <jic23@xxxxxxxxxx> wrote: > On 31/08/16 09:02, Peter Rosin wrote: >> The i2c mux core can then take appropriate action depending on if it is >> used for an actual i2c mux, or for an arbitrator or gate. In this case >> it is used as a gate. >> >> This will make devicetree bindings simpler when they are eventually >> added. >> >> Signed-off-by: Peter Rosin <peda@xxxxxxxxxx> >> --- >> drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> So, this depends on the i2c-mux-dt-3 branch [1] that Jonathan >> pulled to support the new mpu-3050 gyroscope driver. I had >> planned to submit this post 4.9-rc1, but since the iio tree >> got the prerequisite already, I'm sending it right away. > It's not there yet as the mpu-3050 has to go round again > for other reasons. As such I haven't yet pulled your branch. > This patch isn't going to justify the pull on it's own. > > I'll try and remember to pick it up when Linus gets back with > the final mpu-3050 and I pull your tree in. I think it sounds stressy and messy. I'll just hold the driver for v4.10, there is no hurry. Yours, Linus Walleij -- 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
