As wait_for_completion_interruptible_timeout() will be invoked after the first call to i2c_dw_xfer_msg() is made whether or not an error is detected in it, we need to mark ->cmd_complete as completed to avoid a needless HZ timeout. Signed-off-by: Shinya Kuribayashi <shinya.kuribayashi@xxxxxxxxx> --- Or we could change the i2c_dw_xfer_msg() prototype from "void" to "int". Which is preffered? drivers/i2c/busses/i2c-designware.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/drivers/i2c/busses/i2c-designware.c b/drivers/i2c/busses/i2c-designware.c index f7ea032..6f85e28 100644 --- a/drivers/i2c/busses/i2c-designware.c +++ b/drivers/i2c/busses/i2c-designware.c @@ -376,6 +376,7 @@ i2c_dw_xfer_msg(struct dw_i2c_dev *dev) dev_err(dev->dev, "%s: invalid message length\n", __func__); dev->msg_err = -EINVAL; + complete(&dev->cmd_complete); return; } -- 1.6.5 -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
