ONKEY interrupt is trapped in PMU occasionally on resuming

[Andy Green]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
> Somebody in the thread at some point said:
> 
>>> Do you think we have to check the value we read from INT1~INT5? INT2 is
>>> 0xff when this issue occurs, but the EXTON1~EXTON3 is connected to
>>> ground......... 
>> As I know, EXTON1-3 connect to ground was following NXP's instruction in
>> order to avoid battery insert auto-on issue.

> Connecting them to 0V is fine, but if INT2 register comes back as 0xff,

Hi Tony -

In fact these three guys EXTON[1..3] are not connected to ground, we are
the victims of a mass delusion :-)  It was true on A4 but it isn't true
on A5.

If you examine the 20th Dec A5 schematic we see they are pulled up to
VB_SYS via individual 10Ks.  It means they are ~5V when powered from USB.

I was watching EXTON1 when the PMU went into standby during boot, at
that time it went a little crazy... the picture is attached.  But I
don't know it is the real problem because A4 had this problem and it did
have EXTON[1..3] to 0V.

- -Andy

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFHp5AYOjLpvpq7dMoRApvgAJ9CPT3WktFK1p5cuP/Dk1IsYs16ogCeLPkq
XqIutIkw/rmAu6WKWaehReE=
=pFb2
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Name: f0010tek.jpg
Type: image/jpeg
Size: 101973 bytes
Desc: not available
Url : http://lists.openmoko.org/pipermail/openmoko-kernel/attachments/20080204/1f14f3fc/attachment.jpg