Le Mon, 31 Jul 2017 21:17:21 +0200, Wolfram Sang <wsa@xxxxxxxxxxxxx> a écrit : > > +This document is just a brief introduction to the I3C protocol and the concepts > > +it brings on the table. If you need more information, please refer to the MIPI > > +I3C specification. > > I wish I could. > > > + > > +Introduction > > +============ > > + > > +The I3C (I-Cube-C) is a MIPI standardized protocol designed to overcome I2C > > "Eye-three-See", according to: > http://eecatalog.com/sensors/2017/07/05/after-35-years-of-i2c-i3c-improves-capability-and-performance/ I remember hearing eye-cube-see during the discussion we had with Cadence engineers but I might wrong. I'll double check (or maybe I'll just drop any mention of the pronunciation). > > > +Backward compatibility with I2C devices > > +======================================= > > + > > +The I3C protocol has been designed to be backward compatible with I2C devices. > > +This backward compatibility allows one to connect a mix of I2C and I3C devices > > +on the same bus, though, in order to be really efficient, I2C devices should > > +be equipped with 50 ns spike filters. > > I just found a slide which says I3C does not support clock stretching. > That should be mentioned here, too. > You're right, clock stretching is not allowed, and if devices without a 50ns spike filter are connected to the bus, it lowers the maximum speed for all devices, which renders I3C kind of useless. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
