for the controller, as it was copied-and-pasted to become
at91_i2c_probe() in 0bc8f640a4d7ed.
Removing the at91_i2c_probe_chip() function makes the higher layer
(i2c_probe_chip()) try a zero-length read transfer to test for the
presence of a device instead, which does work.
Signed-off-by: Alan
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
Two patches to fix the I2C on SAMA5D3. The first fixes a race
condition in pushing TX data to the hardware, and the second
removes an errant probe_chip function which prevents devices from
being probed properly
These have been tested on master and on 2017.07
Alan Ott (2):
i2c: at91_i2c: Wait
Previously this driver appeared to have been half-way converted to the new
driver model and did not work at all.
Complete the transition to the driver model, adding the necessary
connections.
Signed-off-by: Alan Ott
---
Differences since v1:
* Removed comments around min and max speed
On 06/30/2017 12:00 AM, Jaehoon Chung wrote:
On 06/21/2017 12:23 PM, Alan Ott wrote:
Previously this driver appeared to have been half-way converted to the new
driver model and did not work at all.
Complete the transition to the driver model, adding the necessary
connections.
Signed-off-by
Previously this driver appeared to have been half-way converted to the new
driver model and did not work at all.
Complete the transition to the driver model, adding the necessary
connections.
Signed-off-by: Alan Ott
---
configs/pic32mzdask_defconfig | 1 -
drivers/mmc/Kconfig | 2
6 matches
Mail list logo
