[RFC, PATCH 0/4]: Configuring accelerometer wakeups

[Andy Green]

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

Somebody in the thread at some point said:
| On Mon, 11 Aug 2008 16:00:43 +0100
| Andy Green <andy at openmoko.com> wrote:
|
|> |>    GSTATUS4 0x00000200
|> |>    Interrupt 20
|> |>    gta02_udc_command(1)
|> |
|> | During suspending is triggered and the device therefore resumes
|> | directly. Well, well, at least I have something else to look at
|> | now :-)
|>
|> But the interrupt stuff you mention looks unrelated... 0x200 in
|> GSTATUS4 is EIN9 -> PMU interrupt?  UDC commands come from host PC
|> enumeration action.
|
| Right, but it's the "Interrupt 20" printout that comes from the
| accelerometer - and I think this is what causes it to wakeup
| immediately.

Unless the U-Boot stuff to capture the resume reason is broken, it means
that accel interrupt was not pending when we woke up in U-Boot (but PMU
one was).

| Anyway, I was mostly wondering about the reasons it didn't wakeup
| before - and I know that now, so I'll send a new set of patches when
| I'm ready with the rest.

OK great, drop a note in one about a test procedure and I'll give them a
test run.

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

iEYEARECAAYFAkigdxkACgkQOjLpvpq7dMocAACcDeiKMRif8M/h8IrDIW+L1fS4
gx4An2HU0E4bP4DEZvFjmM4bcBDyX7i0
=wUaK
-----END PGP SIGNATURE-----