From: Marc Kleine-Budde <mkl@pengutronix.de>
To: sha@pengutronix.de
Cc: "Wolfram Sang" <w.sang@pengutronix.de>,
linux-kernel@vger.kernel.org,
"Arnaud Patard" <apatard@mandriva.com>,
linux-i2c@vger.kernel.org,
"Ben Dooks (embedded platforms)" <ben-linux@fluff.org>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Jean Delvare (PC drivers, core)" <khali@linux-fr.org>,
linux-arm-kernel@lists.infradead.org,
"Richard Zhao" <linuxzsc@gmail.com>
Subject: Re: [PATCH V2] i2c-imx: do not allow interruptions when waiting for I2C to complete
Date: Tue, 01 Jun 2010 10:51:16 +0200 [thread overview]
Message-ID: <4C04CA04.6000207@pengutronix.de> (raw)
In-Reply-To: <1274962561-17007-1-git-send-email-mkl@pengutronix.de>
[-- Attachment #1.1: Type: text/plain, Size: 2438 bytes --]
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.
Ping, can someone please comment the patch and/or push upstream.
Marc
>
> 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;
> }
>
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2010-06-01 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 12:16 [PATCH V2] i2c-imx: do not allow interruptions when waiting for I2C to complete Marc Kleine-Budde
2010-06-01 8:51 ` Marc Kleine-Budde [this message]
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=4C04CA04.6000207@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=apatard@mandriva.com \
--cc=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxzsc@gmail.com \
--cc=sha@pengutronix.de \
--cc=u.kleine-koenig@pengutronix.de \
--cc=w.sang@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).