From: Aaro Koskinen <aaro.koskinen@nokia.com>
To: ext Alexander Shishkin <virtuoso@slind.org>
Cc: Tony Lindgren <tony@atomide.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] omap i2c: add timeout to a busy loop in isr
Date: Tue, 15 Dec 2009 15:20:14 +0200 [thread overview]
Message-ID: <4B278D0E.8000807@nokia.com> (raw)
In-Reply-To: <1260796864-8560-1-git-send-email-virtuoso@slind.org>
Hi,
Alexander Shishkin wrote:
> Signed-off-by: Alexander Shishkin <virtuoso@slind.org>
Could you add a better patch description? I.e. the patch is needed
because I2C failure can cause a kernel hang. The problem can be
reproduced by running the bus with wrong (too high) speed.
Also, you should send the patch to ben-linux@fluff.org with
linux-omap and linux-i2c@vger.kernel.org in CC.
Tested-by: Aaro Koskinen <aaro.koskinen@nokia.com>
> drivers/i2c/busses/i2c-omap.c | 21 +++++++++++++--------
> 1 files changed, 13 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
> index 75bf3ad..7617f18 100644
> --- a/drivers/i2c/busses/i2c-omap.c
> +++ b/drivers/i2c/busses/i2c-omap.c
> @@ -803,15 +803,20 @@ complete:
> */
>
> if (dev->rev <= OMAP_I2C_REV_ON_3430) {
> - while (!(stat & OMAP_I2C_STAT_XUDF)) {
> - if (stat & (OMAP_I2C_STAT_NACK | OMAP_I2C_STAT_AL)) {
> - omap_i2c_ack_stat(dev, stat & (OMAP_I2C_STAT_XRDY | OMAP_I2C_STAT_XDR));
> - err |= OMAP_I2C_STAT_XUDF;
> - goto complete;
> - }
> - cpu_relax();
> - stat = omap_i2c_read_reg(dev, OMAP_I2C_STAT_REG);
> + unsigned long timeout = 10000;
I think 10000 reads (with L4 core interconnect latency) is at least 0.8 ms. It should be more than
enough for normal cases.
> + while (!(stat & OMAP_I2C_STAT_XUDF) && --timeout) {
> + if (stat & (OMAP_I2C_STAT_NACK | OMAP_I2C_STAT_AL)) {
> + omap_i2c_ack_stat(dev, stat & (OMAP_I2C_STAT_XRDY | OMAP_I2C_STAT_XDR));
> + err |= OMAP_I2C_STAT_XUDF;
> + goto complete;
> }
> + cpu_relax();
> + stat = omap_i2c_read_reg(dev, OMAP_I2C_STAT_REG);
> + }
> +
> + if (!timeout)
> + dev_err(dev->dev, "timeout waiting on XUDF bit\n");
> }
>
> omap_i2c_write_reg(dev, OMAP_I2C_DATA_REG, w);
A.
prev parent reply other threads:[~2009-12-15 13:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 13:21 [PATCH] omap i2c: add timeout to a busy loop in isr Alexander Shishkin
2009-12-15 13:20 ` Aaro Koskinen [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=4B278D0E.8000807@nokia.com \
--to=aaro.koskinen@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
--cc=virtuoso@slind.org \
/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