[PATCH] motion-sensors-irq-spi.patch

Wolfgang Spraul wolfgang at openmoko.com
Mon Jan 28 15:13:13 CET 2008


OK, so do we believe this list is complete?
Wakup from deep sleep CPU state can be:

1. wifi
2. GSM
3. usb
4. buttons (both AUX and power)
5. motion sensor

Andy, anything else wired up to the EINT[15:0] range?
Wolfgang

On Jan 28, 2008, at 9:53 PM, Andy Green wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Somebody in the thread at some point said:
>> Andy, Werner -
>>
>> today Tony and I wondered whether Motion Sensor activity can wakeup  
>> the
>> CPU from deep sleep.
>> Right now we believe wakeup from deep sleep CPU can be caused by:
>>
>> 1. wifi
>> 2. GSM
>> 3. usb
>>
>> Anything else? We think bluetooth, motion sensors cannot.
>
> I didn't look at this mechanism until now, but it appears from the
> Samsung datasheet that any of the EINT[15:0] interrupts can wake from
> what they call "SLEEP", ie, CPU powered down.
>
> One of the motion sensors interrupts maps to this range (the "top" one
> on GPF0 --> EINT[0]) and one doesn't (the bottom one on GPG8 -->
> EINT[*16*]).
>
> If I understood it then you could probably do something with that if  
> the
> idea is shaking it awake or so on.
>
> - -Andy
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
>
> iD8DBQFHnd5EOjLpvpq7dMoRAivuAJ9tpyE+QJMiXPkKRvQWRUYroRnvQQCeIONI
> jLB/0/P5nDFuiem91UkPIxI=
> =d2za
> -----END PGP SIGNATURE-----





More information about the openmoko-kernel mailing list