From: David Brownell <david-b@pacbell.net>
To: felipe.balbi@nokia.com
Cc: linux-omap@vger.kernel.org
Subject: Re: [patch/rfc/rft 2.6.27-rc8-omap-git] twl4030-pwrirq simplification, cleanup
Date: Mon, 6 Oct 2008 08:51:02 -0700 [thread overview]
Message-ID: <200810060851.03269.david-b@pacbell.net> (raw)
In-Reply-To: <20081006084609.GD7437@gandalf.research.nokia.com>
On Monday 06 October 2008, Felipe Balbi wrote:
> On Mon, Oct 06, 2008 at 01:19:18AM -0700, David Brownell wrote:
> > ...
> >
> > (This is similar to the GPIO patch I just sent, but simpler
> > except for the impact on the few drivers thinking oddly
> > about IRQs. Those patches cover the key SIH modules, and
> > a similar one affects the PIH in twl4030-core.)
>
> What are the dependencies for this patch ? It doesn't apply cleanly.
Applies against current GIT with a few minor offsets caused
by the patch working around the i2c-omap timeouts. I've sent
that before; it's appended for reference.
---
drivers/i2c/chips/twl4030-pwrirq.c | 10 ++++++++++
1 file changed, 10 insertions(+)
--- a/drivers/i2c/chips/twl4030-pwrirq.c
+++ b/drivers/i2c/chips/twl4030-pwrirq.c
@@ -161,6 +161,8 @@ static int twl4030_pwrirq_thread(void *d
return 0;
}
+#include <linux/delay.h>
+
static int __init twl4030_pwrirq_init(void)
{
int i, err;
@@ -168,8 +170,16 @@ static int __init twl4030_pwrirq_init(vo
twl4030_pwrirq_mask = 0xff;
twl4030_pwrirq_pending_unmask = 0;
+/* HEY: core already did this.
+ * But that's surely not why we
+ * sometimes see i2c timeouts here ...
+ */
+for (i = 0; i < 5; i++) {
err = twl4030_i2c_write_u8(TWL4030_MODULE_INT, twl4030_pwrirq_mask,
TWL4030_INT_PWR_IMR1);
+if (!err) break;
+msleep(10);
+}
if (err)
return err;
next prev parent reply other threads:[~2008-10-06 15:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 8:19 [patch/rfc/rft 2.6.27-rc8-omap-git] twl4030-pwrirq simplification, cleanup David Brownell
2008-10-06 8:46 ` Felipe Balbi
2008-10-06 15:51 ` David Brownell [this message]
2008-10-10 11:56 ` 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=200810060851.03269.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.