[PATCH 0/3] RFC: fix bug http://docs.openmoko.org/trac/ticket/1884
andy at openmoko.com
Fri Nov 14 15:11:13 CET 2008
-----BEGIN PGP SIGNED MESSAGE-----
Somebody in the thread at some point said:
| Andy Green wrote:
|> 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...
| Yeah, I had that on my list of things to try. Just did it. Nope,
| doesn't help :-(
| I'll repeat it later with the scope watching, though.
It's worth using the scope to confirm that the 1-bit mode was actually
used at all.
Another trick that might be interesting then would be now D1 is "clean"
interrupt signal assuming the 1-bit thing worked, could be toggling a
GPIO somewhere in the ISR, and looking at that and D1 on the scope.
Assuming the D1 interrupts are happening at long intervals the
relationship of any spamming in the ISR to D1 might give a clue.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the openmoko-kernel