Re: [PATCH] twl4030: Fix pwrirq by making sure the module is responding (Re: kernel oops for 3430sdp)

[David Brownell <david-b@pacbell.net>]

On Wednesday 08 October 2008, Tony Lindgren wrote:
> > 
> > Well, there does seem to be an issue where the "pending IRQ" mechanism
> > can leave a PWRIRQ.PWRON interrupt pending sometimes.  If you see a
> > bunch of alarming-but-harmless boot messages like 
> > 
> >   TWL4030 module irq 373 is disabled but can't be masked!
> > 
> > before pwrirq registers, that seems to be the issue.  A debug hack I
> > applied (appended) reported that the mask (IMR) was 0xff but the IRQ
> > was still being raised ... when pwrirq registered itself, the stream
> > of those messages stopped.  (Or, when this hack dumped the status and
> > thus kicked in clear-on-read ...)
> 
> Hmm, maybe there's some status register for each modules that should be
> checked?

I think this was just a natural consequence of PENDDIS=0 in the
SIH_CTRL register.  A minor annoyance in the init sequence since
it causes extra IRQs, but nothing significant.

I haven't come across a TWL register that could explain I2C
timeouts.  At least, not yet.

- Dave

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html