Thank you for the informative reply. I was unfamiliar with the new mux and parent locking schemes. They do make the solution for this problem much easier to deal with. I'm working with release 4.4 (Ubuntu Xenial), so the mux/parent locking hadn't shown up on my radar yet. Unfortunately, the target release for my work is and will remain 4.4 for a while. Regards, Mike On Thu, Nov 10, 2016 at 8:01 AM, Peter Rosin <peda@xxxxxxxxxx> wrote: >> There is however one requirement, the CPLD-mux must be "mux-locked" >> as explained in Documentation/i2c/i2c-topology. Otherwise accesses >> to devices behind that mux will lock the PCA9547 mux for the full >> duration of the transaction and thus lock out any attempts to update >> the CPLD mux as part of the transaction. -- 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
