From: Ben Dooks <ben-linux@fluff.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: "Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
Sascha Hauer <sha@pengutronix.de>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] i2c-imx: do not allow interruptions when waiting for I2C to complete (resend)
Date: Sun, 20 Jun 2010 23:33:21 +0100 [thread overview]
Message-ID: <20100620223321.GA12387@fluff.org.uk> (raw)
In-Reply-To: <4C1753F6.3080106@pengutronix.de>
On Tue, Jun 15, 2010 at 12:20:38PM +0200, Marc Kleine-Budde wrote:
> The i2c_imx_trx_complete() function is using
> wait_event_interruptible_timeout() to wait for the I2C controller to
> signal that it has completed an I2C bus operation. If the process that
> causes the I2C operation receives a signal, the wait will be
> interrupted, returning an error. It is better to let the I2C operation
> finished before handling the signal (i.e. returning into userspace).
>
> It is safe to use wait_event_timeout() instead, because the timeout
> will allow the process to exit if the I2C bus hangs. It's also better
> to allow the I2C operation to finish, because unacknowledged I2C
> operations can cause the I2C bus to hang.
Hmm, if it times out, do you need to at-least try sending a stop
on the bus? or does the caller do that for you?
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
> Reviewed-by: Wolfram Sang <w.sang@pengutronix.de>
> ---
>
> V2: Remove check for "result < 0" as commented by Wolfram Sang.
>
> drivers/i2c/busses/i2c-imx.c | 9 +++------
> 1 files changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-imx.c b/drivers/i2c/busses/i2c-imx.c
> index d1ff940..58df809 100644
> --- a/drivers/i2c/busses/i2c-imx.c
> +++ b/drivers/i2c/busses/i2c-imx.c
> @@ -161,13 +161,10 @@ static int i2c_imx_trx_complete(struct
> imx_i2c_struct *i2c_imx)
> {
> int result;
>
> - result = wait_event_interruptible_timeout(i2c_imx->queue,
> + result = wait_event_timeout(i2c_imx->queue,
> i2c_imx->i2csr & I2SR_IIF, HZ / 10);
>
> - if (unlikely(result < 0)) {
> - dev_dbg(&i2c_imx->adapter.dev, "<%s> result < 0\n", __func__);
> - return result;
> - } else if (unlikely(!(i2c_imx->i2csr & I2SR_IIF))) {
> + if (unlikely(!(i2c_imx->i2csr & I2SR_IIF))) {
> dev_dbg(&i2c_imx->adapter.dev, "<%s> Timeout\n", __func__);
> return -ETIMEDOUT;
> }
> @@ -295,7 +292,7 @@ static irqreturn_t i2c_imx_isr(int irq, void *dev_id)
> i2c_imx->i2csr = temp;
> temp &= ~I2SR_IIF;
> writeb(temp, i2c_imx->base + IMX_I2C_I2SR);
> - wake_up_interruptible(&i2c_imx->queue);
> + wake_up(&i2c_imx->queue);
> return IRQ_HANDLED;
> }
>
> --
> 1.7.1
>
--
Ben (ben@fluff.org, http://www.fluff.org/)
'a smiley only costs 4 bytes'
next prev parent reply other threads:[~2010-06-20 22:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-15 10:20 [PATCH V2] i2c-imx: do not allow interruptions when waiting for I2C to complete (resend) Marc Kleine-Budde
2010-06-20 22:33 ` Ben Dooks [this message]
[not found] ` <20100620223321.GA12387-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2010-06-21 7:07 ` Marc Kleine-Budde
[not found] ` <4C1F0FC7.60605-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-06-21 7:27 ` [PATCH V3] i2c-imx: do not allow interruptions when waiting for I2C to complete Marc Kleine-Budde
2010-07-15 7:49 ` [PATCH V3 RESEND] " Marc Kleine-Budde
2010-07-19 8:11 ` [PATCH V3 RESEND2] " Marc Kleine-Budde
2010-09-15 11:45 ` [PATCH V3 RESEND3] " Marc Kleine-Budde
2010-09-24 14:50 ` [PATCH V3 RESEND4] " Marc Kleine-Budde
[not found] ` <4C9CBAA1.5040202-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-09-28 9:05 ` Wolfram Sang
2010-10-04 14:22 ` [PATCH V3 RESEND5] " Marc Kleine-Budde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100620223321.GA12387@fluff.org.uk \
--to=ben-linux@fluff.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=sha@pengutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).