i2c: imx: fix i2c issues when reading messages
Status from this message: merged to i2c/i2c-host-fixes.
Get series with b4
b4 am [email protected]Versions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | i2c: imx: fix i2c issue when reading multiple messagesdrivers/ | +1 | 1 reply | |
| 2/2 | i2c: imx: ensure no clock is generated after last readdrivers/ | +32 | 7 replies |
Reviews trailers per patch
1 of 2 patches has a Reviewed-by or Acked-by.
| Patch | Frank Li |
|---|---|
| 1/2 | R-b |
| 2/2 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH v1 0/2] i2c: imx: fix i2c issues when reading messages
This patch series fixes two issues with the imx i2c driver when reading messages.
The first issue is that after a repeated start the bus is still busy. If the driver polls for that bus busy bit, the driver will timeout and fail to read.
The second issue is that after the last message the driver should not immediately read the data from the data register or an additional clock will be generated. This can cause devices that react to that clock to misbehave which will also lead to a timeout.
Stefan Eichenberger (2):
i2c: imx: fix i2c issue when reading multiple messages
i2c: imx: ensure no clock is generated after last read
drivers/i2c/busses/i2c-imx.c | 51 ++++++++++++++++++++++-------------- 1 file changed, 32 insertions(+), 19 deletions(-)
Signature · 1 line
2.51.0