Re: [U-Boot] [PATCH 1/2] i2c: at91_i2c: Wait for TXRDY after sending the first byte

2017-12-07 Thread Heiko Schocher
Hello Alan, Am 29.11.2017 um 04:25 schrieb Alan Ott: The driver must wait for TXRDY after each byte is pushed into the i2c FIFO before pushing the next byte. Previously this was not done for the first byte, causing a race condition with zeros sometimes being sent for the next byte (which is typi

Re: [U-Boot] [PATCH 1/2] i2c: at91_i2c: Wait for TXRDY after sending the first byte

2017-12-07 Thread Heiko Schocher
Hello Alan, Am 29.11.2017 um 04:25 schrieb Alan Ott: The driver must wait for TXRDY after each byte is pushed into the i2c FIFO before pushing the next byte. Previously this was not done for the first byte, causing a race condition with zeros sometimes being sent for the next byte (which is typi

Re: [U-Boot] [PATCH 1/2] i2c: at91_i2c: Wait for TXRDY after sending the first byte

2017-11-29 Thread Yang, Wenyou
On 2017/11/29 11:25, Alan Ott wrote: The driver must wait for TXRDY after each byte is pushed into the i2c FIFO before pushing the next byte. Previously this was not done for the first byte, causing a race condition with zeros sometimes being sent for the next byte (which is typically the first

[U-Boot] [PATCH 1/2] i2c: at91_i2c: Wait for TXRDY after sending the first byte

2017-11-28 Thread Alan Ott
The driver must wait for TXRDY after each byte is pushed into the i2c FIFO before pushing the next byte. Previously this was not done for the first byte, causing a race condition with zeros sometimes being sent for the next byte (which is typically the first actual data byte). Signed-off-by: Alan