On 23.08.2016 09:37, Peter Rosin wrote:
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
Hmm. Depends a bit on timing. The merge window close for IIO is in
perhaps 3 weeks time. If this driver isn't ready reasonably quickly
I'll probably hold it for next window anyway.
If we do want to do the mux stuff and this in the same window then
the standard trick is a branch with just the relevant patches that
are the dependency in it and we both merge that into our trees.
Key thing is that we then don't touch this branch at all.
Git then sorts the mess out just fine when that works it's way to
Linus. The two trees will have the same commit id's for the patches
so he'll get them via which ever tree he merges first.
Jonathan
--
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
