From: Tony Lindgren <tony@atomide.com>
To: ben-linux@fluff.org
Cc: linux-i2c@vger.kernel.org, linux-omap@vger.kernel.org,
Jarkko Nikula <jarkko.nikula@nokia.com>,
Juha Yrjola <juha.yrjola@solidboot.com>,
Tony Lindgren <tony@atomide.com>
Subject: [PATCH 1/10] i2c-omap: Do not use interruptible wait call in omap_i2c_xfer_msg
Date: Thu, 30 Oct 2008 19:29:40 -0700 [thread overview]
Message-ID: <1225420189-630-2-git-send-email-tony@atomide.com> (raw)
In-Reply-To: <1225420189-630-1-git-send-email-tony@atomide.com>
From: Jarkko Nikula <jarkko.nikula@nokia.com>
If there is a signal pending and wait_for_completion_interruptible_timeout
terminates with -ERESTARTSYS, we return and disable the i2c clocks in
omap_i2c_xfer.
If we terminate before sending last i2c message with a stop condition, the
bus remains busy and we are not able to send new messages into bus with
successive omap_i2c_xfer calls. Therefore a pending signal is not caught
here and we return only because of timeout or i2c error.
Signed-off-by: Jarkko Nikula <jarkko.nikula@nokia.com>
Signed-off-by: Juha Yrjola <juha.yrjola@solidboot.com>
Signed-off-by: Tony Lindgren <tony@atomide.com>
---
drivers/i2c/busses/i2c-omap.c | 8 ++++++--
1 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-omap.c b/drivers/i2c/busses/i2c-omap.c
index 608038d..17476ec 100644
--- a/drivers/i2c/busses/i2c-omap.c
+++ b/drivers/i2c/busses/i2c-omap.c
@@ -328,8 +328,12 @@ static int omap_i2c_xfer_msg(struct i2c_adapter *adap,
w |= OMAP_I2C_CON_STP;
omap_i2c_write_reg(dev, OMAP_I2C_CON_REG, w);
- r = wait_for_completion_interruptible_timeout(&dev->cmd_complete,
- OMAP_I2C_TIMEOUT);
+ /*
+ * REVISIT: We should abort the transfer on signals, but the bus goes
+ * into arbitration and we're currently unable to recover from it.
+ */
+ r = wait_for_completion_timeout(&dev->cmd_complete,
+ OMAP_I2C_TIMEOUT);
dev->buf_len = 0;
if (r < 0)
return r;
--
1.5.6.rc3.21.g8c6b5
next prev parent reply other threads:[~2008-10-31 2:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 2:29 [PATCH 0/10] git-pull-request for i2c-omap fixes and updates, v3 Tony Lindgren
2008-10-31 2:29 ` Tony Lindgren [this message]
2008-10-31 2:29 ` [PATCH 2/10] i2c-omap: Close suspected race between omap_i2c_idle() and omap_i2c_isr() Tony Lindgren
2008-10-31 2:29 ` [PATCH 3/10] i2c-omap: Add high-speed support to omap-i2c Tony Lindgren
2008-10-31 2:29 ` [PATCH 4/10] i2c-omap: FIFO handling support and broken hw workaround for i2c-omap Tony Lindgren
2008-10-31 2:29 ` [PATCH 5/10] i2c-omap: Add support for omap34xx Tony Lindgren
2008-10-31 2:29 ` [PATCH 6/10] i2c-omap: Mark init-only functions as __init Tony Lindgren
2008-10-31 2:29 ` [PATCH 7/10] i2c-omap: Don't compile in OMAP15xx I2C ISR for non-OMAP15xx builds Tony Lindgren
2008-10-31 2:29 ` [PATCH 8/10] i2c-omap: Clean-up i2c-omap Tony Lindgren
2008-10-31 2:29 ` [PATCH 9/10] i2c-omap: fix I2C timeouts due to recursive omap_i2c_{un,}idle() Tony Lindgren
2008-10-31 2:29 ` [PATCH 10/10] I2C: Ensure write posting for critical i2c-omap writes Tony Lindgren
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=1225420189-630-2-git-send-email-tony@atomide.com \
--to=tony@atomide.com \
--cc=ben-linux@fluff.org \
--cc=jarkko.nikula@nokia.com \
--cc=juha.yrjola@solidboot.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-omap@vger.kernel.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