From: Tony Lindgren <tony@atomide.com>
To: Alexander Shishkin <virtuoso@slind.org>
Cc: ben-linux@fluff.org, nm@ti.com, linux-omap@vger.kernel.org,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v2 2/2] omap i2c: add a timeout to the busy waiting
Date: Mon, 28 Dec 2009 16:15:33 -0800 [thread overview]
Message-ID: <20091229001533.GV3512@atomide.com> (raw)
In-Reply-To: <1261394999-20857-3-git-send-email-virtuoso@slind.org>
* Alexander Shishkin <virtuoso@slind.org> [091221 03:30]:
> The errata 1.153 workaround is busy waiting on XUDF bit in interrupt
> context, which may lead to kernel hangs. The problem can be reproduced
> by running the bus with wrong (too high) speed.
>
> Signed-off-by: Alexander Shishkin <virtuoso@slind.org>
> CC: linux-i2c@vger.kernel.org
> CC: linux-omap@vger.kernel.org
> CC: nm@ti.com
Acked-by: Tony Lindgren <tony@atomide.com>
> ---
> drivers/i2c/busses/i2c-omap.c | 8 ++++++++
> 1 files changed, 8 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
> index 2d146ac..7d56a25 100644
> --- a/drivers/i2c/busses/i2c-omap.c
> +++ b/drivers/i2c/busses/i2c-omap.c
> @@ -678,6 +678,8 @@ omap_i2c_rev1_isr(int this_irq, void *dev_id)
> */
> static int errata_omap3_1p153(struct omap_i2c_dev *dev, u16 *stat, int *err)
> {
> + unsigned long timeout = jiffies + msecs_to_jiffies(1);
> +
> 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 |
> @@ -685,6 +687,12 @@ static int errata_omap3_1p153(struct omap_i2c_dev *dev, u16 *stat, int *err)
> *err |= OMAP_I2C_STAT_XUDF;
> return -ETIMEDOUT;
> }
> +
> + if (time_after(jiffies, timeout)) {
> + dev_err(dev->dev, "timeout waiting on XUDF bit\n");
> + return 0;
> + }
> +
> cpu_relax();
> *stat = omap_i2c_read_reg(dev, OMAP_I2C_STAT_REG);
> }
> --
> 1.6.3.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-12-29 0:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 11:29 [PATCH v2 0/2] omap i2c interrupt handler fixes Alexander Shishkin
2009-12-21 11:29 ` [PATCH v2 1/2] omap i2c: make errata 1.153 workaround a separate function Alexander Shishkin
2009-12-21 11:29 ` [PATCH v2 2/2] omap i2c: add a timeout to the busy waiting Alexander Shishkin
2009-12-29 0:15 ` Tony Lindgren [this message]
[not found] ` <1261394999-20857-2-git-send-email-virtuoso-0lOfPCoBze7YtjvyW6yDsg@public.gmane.org>
2009-12-29 0:13 ` [PATCH v2 1/2] omap i2c: make errata 1.153 workaround a separate function Tony Lindgren
2010-01-05 17:05 ` Alexander Shishkin
-- strict thread matches above, loose matches on Subject: below --
2010-03-16 14:30 [PATCH " Tony Lindgren
[not found] ` <20100316143025.GR2900-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2010-03-25 9:52 ` [PATCH v2 2/2] omap i2c: add a timeout to the busy waiting Alexander Shishkin
[not found] ` <1269510757-8119-3-git-send-email-virtuoso-0lOfPCoBze7YtjvyW6yDsg@public.gmane.org>
2010-03-25 14:38 ` Aaro Koskinen
[not found] ` <4BAB7551.6040203-xNZwKgViW5gAvxtiuMwx3w@public.gmane.org>
2010-03-25 15:02 ` Alexander Shishkin
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=20091229001533.GV3512@atomide.com \
--to=tony@atomide.com \
--cc=ben-linux@fluff.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.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;
as well as URLs for NNTP newsgroup(s).