On Tue, May 09, 2017 at 02:03:51PM +0200, Joakim Tjernlund wrote: > Current I2C reset procedure is broken in two ways: > 1) It only generate 1 START instead of 9 STARTs and STOP. > 2) It leaves the bus Busy so every I2C xfer after the first > fixup calls the reset routine again, for every xfer there after. > > This fixes both errors. Add an iobarrier_rw() when writing the > I2C control register as well to make sure the register reaches the > controller in time. > > Signed-off-by: Joakim Tjernlund BTW can this driver be converted to make use of the bus_recovery infrastructure?