UCD3138064: I2C function miss data when doing sequential read

Kevin, I've heard of something like this, but haven't seen any tests, so it's probably true.  I'm not aware of any way to stop the clock.  Generally you can limit the number of bytes returned to 4 bytes per message, and it will slow down throughput somewhat, but you won't miss anything.  If you can service the data ready bit fast enough, you can still catch all the bytes for longer messages.  We have tested it with interrupts in simulation, and with fast polling on the chip, and both of those work.