diff options
author | Cyrille Pitchen <cyrille.pitchen@atmel.com> | 2015-10-21 15:44:03 +0200 |
---|---|---|
committer | Wolfram Sang <wsa@the-dreams.de> | 2015-10-22 15:14:41 +0200 |
commit | 6f6ddbb09d2a5baded0e23add3ad2d9e9417ab30 (patch) | |
tree | cf445aa30b119bec768cf94a0bcac6e37fb679a2 /arch/score | |
parent | 319d7f05dfb148935de46f2c7544ecf1e6332161 (diff) | |
download | linux-6f6ddbb09d2a5baded0e23add3ad2d9e9417ab30.tar.bz2 |
i2c: at91: fix write transfers by clearing pending interrupt first
In some cases a NACK interrupt may be pending in the Status Register (SR)
as a result of a previous transfer. However at91_do_twi_transfer() did not
read the SR to clear pending interruptions before starting a new transfer.
Hence a NACK interrupt rose as soon as it was enabled again at the I2C
controller level, resulting in a wrong sequence of operations and strange
patterns of behaviour on the I2C bus, such as a clock stretch followed by
a restart of the transfer.
This first issue occurred with both DMA and PIO write transfers.
Also when a NACK error was detected during a PIO write transfer, the
interrupt handler used to wrongly start a new transfer by writing into the
Transmit Holding Register (THR). Then the I2C slave was likely to reply
with a second NACK.
This second issue is fixed in atmel_twi_interrupt() by handling the TXRDY
status bit only if both the TXCOMP and NACK status bits are cleared.
Tested with a at24 eeprom on sama5d36ek board running a linux-4.1-at91
kernel image. Adapted to linux-next.
Reported-by: Peter Rosin <peda@lysator.liu.se>
Signed-off-by: Cyrille Pitchen <cyrille.pitchen@atmel.com>
Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
Tested-by: Peter Rosin <peda@lysator.liu.se>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Fixes: 93563a6a71bb ("i2c: at91: fix a race condition when using the DMA controller")
Cc: stable@vger.kernel.org #4.1
Diffstat (limited to 'arch/score')
0 files changed, 0 insertions, 0 deletions