> Still, as of now we can't consider what Alexander mentions a bug. Good
> to get it sorted out, but not -rc material.
>
Actually, I focused on fixing issues then i2c-omap acts as master in a multi master environment.
And must say, that current linux/mainline driver work perfectly with minor fixes.
I could take a look how to switch the driver into mixed master/slave mode, but later.
Sad to say, I encountered undocumented i2c- hardware issue.
In short: BB-bit doesn't reflect I2C-bus state after soft reset if SDA or SCL line was low during reset
until i2c-controller again detect START or STOP condition on the wire.
More over, if SDA was low during reset, than next submitted transfer will not start ("controller timeout"),
if SCL was low during reset, than next submitted transfer will start and corrupt signals on wire :(
I'm checking it now. And going to post results to ti forum.
BB-bit reflect I2C-bus state, between power-down/power-up modes.
Alexander.--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
