From: David Brownell <david-b@pacbell.net>
To: Nathan Monson <nmonson@gmail.com>
Cc: Tony Lindgren <tony@atomide.com>,
Felipe Balbi <felipe.balbi@nokia.com>,
linux-omap@vger.kernel.org
Subject: Re: [patch 2.6.27-rc7-omap1-git 1/2] twl4030-core: move to drivers/mfd
Date: Fri, 3 Oct 2008 15:16:31 -0700 [thread overview]
Message-ID: <200810031516.32367.david-b@pacbell.net> (raw)
In-Reply-To: <e5e6ade50810031312o4cd37f4fhc5f2204f31af8dbb@mail.gmail.com>
On Friday 03 October 2008, Nathan Monson wrote:
> can't get IRQ 378, err -22
> twl4030_usb: probe of twl4030_usb failed with error -22
> Unable to allocate IRQ for power button
>
> This is a stock linux-omap with no patches.
Did you see "i2c_omap i2c_omap.1: controller timed out"
earlier in the boot sequence? It would have this symptom,
among others... Earlier in this thread you'll find:
http://marc.info/?l=linux-omap&m=122297833314280&w=2
commenting on the issue I noted when I posted this patch;
showing how I work around that specific I2C error. It'd
likely work for you too.
I've seen this i2c adapter hit such failures in other
places too, but that location is more reproducible.
And it has relatively *visible* nasty side effects...
- Dave
p.s. Shades of OMAP1 I2C problems! I recall similar
cases of the I2C adapter driver stumbling during
boot and thus making registrations fail. The
same workaround (retry) solved things then too...
next prev parent reply other threads:[~2008-10-03 22:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-02 2:47 [patch 2.6.27-rc7-omap1-git 1/2] twl4030-core: move to drivers/mfd David Brownell
2008-10-02 9:07 ` Felipe Balbi
2008-10-02 14:52 ` David Brownell
2008-10-02 14:53 ` Felipe Balbi
2008-10-03 13:37 ` Tony Lindgren
2008-10-03 20:12 ` Nathan Monson
2008-10-03 22:16 ` David Brownell [this message]
2008-10-03 23:31 ` Nathan Monson
2008-10-04 0:00 ` David Brownell
2008-10-02 19:47 ` David Brownell
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=200810031516.32367.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=felipe.balbi@nokia.com \
--cc=linux-omap@vger.kernel.org \
--cc=nmonson@gmail.com \
--cc=tony@atomide.com \
/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