> I haven't managed to reproduce it on i2c. I reproduced a similar behavior
> while working on renesas-i3c driver and decided to implement this on this
> i2c driver as well.

I think the issue is real, but I am not convinced the solution is
complete without a verified testcase.

Maybe it is not too hard to test: you could hack the timeout to be lower
and then write a block of data to an EEPROM. Its erase cycle can trigger
the timeout then...