Tiago Beling d'Avila

This issue was very well described a few years ago #254 on the old SoC BCM2835, but the description is still exactly the same as the new SoC BCM2711 used...

> Your "Steps to reproduce the behaviour" does not include the step "find some hardware that uses I2C clock stretching. We're not about to go and spend significant money on...

> Guys, If you need testing-hardware, let me know and I'll ship you a module. You're not having to spend a cent on that. I'll sponsor "quick testing by those...

> I've just checked with @P33M as the person with probably the most knowledge about this (hopefully he'll correct me if I report this wrong). > > Recollection is that...

> AIUI, these are new I2C controllers on the 2711, above what is present on earlier SoC's. The older controllers with the faults are still there, but the additional ones...

After setting the i2c to use alt5 by editing `/boot/config.txt` adding `dtoverlay=i2c3,pins_2_3,baudrate=40000` at first, the stretch was corrected. However I am observing a strange alternation in the clock frequency. As...

I fixed the core clock and set the i2c baudrate to 10000bps and run a strees test on the device reading that frequently uses stretch. It decreased drastically but eventually...

We also experiencing this too. We keep waiting. This feature is vital for using OAuth during the testing process where self-signed certificates are used.

We have also been waiting for this feature for many years and it would bring a huge improvement in the experience already described very well by @DavidJRobertson. We cannot imagine...