Hi, > > At the moment perhaps the strongest argument for why this particular > > arbitration scheme is needed is that's what the EC (embedded > > controller) on the ARM Chromebook uses. There have been several > > arguments in-house about whether this was the most ideal way to > > structure things, but that's what we shipped with. Thus, if we want > > to be able to talk to i2c devices on this bus (contains the keyboard, > > battery, and a bunch of power switches) we need something in the > > system that implements this arbitration scheme. > > > > There was some discussion about using the built-in I2C multi-master > support but no one had had a good experience getting it to work > reliably in a real system so we ended up deciding not to rely on this.
So, were there no experiences at all or bad experiences when trying? I am interested in hearing what I2C multi master restrictions might exist in practice. Thanks, Wolfram -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
