[PATCH] add-resume-reason-sysfs.patch

andrzej zaborowski balrogg at gmail.com
Wed May 21 00:14:15 CEST 2008

On 20/05/2008, joerg at openmoko.org <joerg at openmoko.org> wrote:
> Am Mo  19. Mai 2008 schrieb Andy Green:
>  > The lower case ones under PMU are PMU interrupt sources that are
>  > "hidden" inside a single interrupt pin that reaches the CPU from the
>  > PMU, they're documented in the pcf50633 datasheet you can hopefully
>  > still get from here:
>  >
>  > http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware
>  >
>  > Only a very few of those are enabled for wake when
>  > fix-reduce-wake-reasons-in-pcf50633.patch goes in stable:
>  >
>  > ~ - USB insertion
>  > ~ - USB removal
>  > ~ - RTC Alarm
>  > ~ - Power key pressed
>  > ~ - Power key pressed for 1s  (hm oh well)
>  >
>  > "second" is a 1s heartbeat interrupt you can enable, but it isn't used
>  > for wake.  I listed everything in case things accidentally get enabled
>  > for wake in the future.
>  what's going to happen, when I power up the device by powerbutton (let's say
>  from suspend), and a few (milli)"seconds" later the RTC Alarm incidentally
>  triggers. What will the handler that's supposed to deal with RTC events see
>  when looking for wake cause? Can it tell the device was already powered up by
>  user?

In Andy's patch I think various reasons can be indicated as true,
that's why the whole list is printed everytime.  Probably not the
easiest format to parse, but usable.

When the button and alarm events occur in a distance of milliseconds,
for the user they happened at the same time and the software probably
shouldn't do any decision based on which came first, or it's a timing
issue for the user.

Please do not print this email unless absolutely necessary. Spread
environmental awareness.

More information about the openmoko-kernel mailing list