[PATCH 0/3] RFC: fix bug http://docs.openmoko.org/trac/ticket/1884

Andy Green andy at openmoko.com
Fri Nov 14 11:08:34 CET 2008

Hash: SHA1

Somebody in the thread at some point said:
| Andy Green wrote:
|> It'd be neat if this was behind the other funnies with level interrupts
|> seen earlier in the year.
| I have some vague recollection that we had some issues there, but
| nothing specific pops up in my mind. Do you remember some places
| worth looking at ?

It was pcf50633, motion sensors and something else (glamo?) all had this
storm behaviour like Matt reports with level, but it's like Feb or March
2008 or so.  Details were probably pretty hazy even at the time.

| By the way, I also tried this with the SDIO interrupt problem, which
| would fit the "things go horribly wrong for no good reason" category

About these fake interrupts, SDIO uses D1 to signal async interrupt...
does SDIO allow 1-bit data mode?  If you can just select it as a flag to
the host controller stuff, it will allow to confirm that the problem
doesn't come from data traffic on D1 being wrongly understood as
interrupt request actions...

- -Andy
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org


More information about the openmoko-kernel mailing list