From: Tony Lindgren <tony@atomide.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Koen Kooi <k.kooi@student.utwente.nl>,
linux-omap@vger.kernel.org, felipe.balbi@nokia.com,
peter.de-schrijver@nokia.com,
Beagle Board <beagleboard@googlegroups.com>
Subject: Re: TWL4030 intermittent freakout on boot
Date: Thu, 8 May 2008 11:42:59 -0700 [thread overview]
Message-ID: <20080508184258.GF24454@atomide.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0805081229440.27986@utopia.booyaka.com>
* Paul Walmsley <paul@pwsan.com> [080508 11:33]:
> On Thu, 8 May 2008, Tony Lindgren wrote:
>
> > This also looks similar to the earlier twl4030 hangs where access
> > to some domains caused twl4030 to hang. If twl4030 hangs, there's
> > no way to reset it as all control is over I2C. When twl4030 hangs,
> > bootloader won't be able to detect the chip either unless devices
> > is power cycled (and USB cable detached).
> >
> > The reason earlier was that twl4030 internal clock was not being
> > programmed properly, and was fixed by patch
> > 0d81cf7e804c529c58d3054c1b9bdb7b3f1dec5d.
> >
> > Maybe there's some twl4030 register access going on before the
> > internal clock is programmed properly?
>
> IRQ 56 is the TWL4030 I2C1 IRQ. Seems strange that there would be no
> handler for it after i2c_omap has initialized...
Well if the I2C register access hangs, nothing will be able to reset
the twl4030 interrupt registers when an interrupt happens.
Tony
next prev parent reply other threads:[~2008-05-08 18:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 18:13 TWL4030 intermittent freakout on boot Paul Walmsley
2008-05-08 18:20 ` Koen Kooi
2008-05-08 18:28 ` Tony Lindgren
2008-05-08 18:33 ` Paul Walmsley
2008-05-08 18:42 ` Tony Lindgren [this message]
2008-05-09 18:08 ` [beagleboard] " Dirk Behme
2008-05-09 21:36 ` Tony Lindgren
2008-05-09 23:11 ` Steve Sakoman
2008-05-10 9:37 ` Dirk Behme
2008-05-10 13:42 ` Steve Sakoman
2008-05-10 14:57 ` Woodruff, Richard
2008-05-10 15:16 ` Koen Kooi
2008-05-10 9:33 ` Koen Kooi
2008-05-12 16:10 ` Tony Lindgren
2008-05-12 16:17 ` Koen Kooi
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=20080508184258.GF24454@atomide.com \
--to=tony@atomide.com \
--cc=beagleboard@googlegroups.com \
--cc=felipe.balbi@nokia.com \
--cc=k.kooi@student.utwente.nl \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=peter.de-schrijver@nokia.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