[lkml]   [2014]   [Mar]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Patch in this message
Subject[PATCH] i2c-cadence: Do not let signals interrupt I2C transfers
Pressing CTRL-C while communicating with an I2C device leads to erratic
behaviour. The cause is that the controller will interrupt the I2C transfer
in progress, and leave the client device in an undefined state. Many
drivers do not handle error return codes on I2C transfers. The calling driver
has no way of telling how much of the transfer has actually completed, so
it cannot reliably determine the device's state.

The best solution here is to not handle signals in the I2C bus driver at all,
but always complete a transaction before returning control.

See for a related patch and discussion on this topic:

Signed-off-by: Mike Looijmans <>
drivers/i2c/busses/i2c-cadence.c | 12 ++++--------
1 file changed, 4 insertions(+), 8 deletions(-)

diff --git a/drivers/i2c/busses/i2c-cadence.c b/drivers/i2c/busses/i2c-cadence.c
index 86713d6..c61c3c9 100644
--- a/drivers/i2c/busses/i2c-cadence.c
+++ b/drivers/i2c/busses/i2c-cadence.c
@@ -452,16 +452,12 @@ static int cdns_i2c_process_msg(struct cdns_i2c *id, struct i2c_msg *msg,

/* Wait for the signal of completion */
- ret = wait_for_completion_interruptible_timeout(
- &id->xfer_done, HZ);
- if (ret < 1) {
+ ret = wait_for_completion_timeout(&id->xfer_done, HZ);
+ if (!ret) {
- if (!ret) {
- dev_err(id->,
+ dev_err(id->,
"timeout waiting on completion\n");
- return -ETIMEDOUT;
- }
- return ret;
+ return -ETIMEDOUT;

 \ /
  Last update: 2014-03-11 09:26    [W:0.059 / U:1.612 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site