Openmoko Bug #81: Decide how PMU RTC alarm interrupt is signalled to userspace

[Openmoko Public Trac]

#81: Decide how PMU RTC alarm interrupt is signalled to userspace
-------------------------------------+--------------------------------------
    Reporter:  laforge@…             |        Owner:  werner          
        Type:  defect                |       Status:  closed          
    Priority:  high                  |    Milestone:                  
   Component:  System Software       |      Version:  current svn head
    Severity:  major                 |   Resolution:  fixed           
    Keywords:                        |     Haspatch:  0               
   Blockedby:                        |    Estimated:                  
 Patchreview:                        |     Blocking:                  
Reproducible:                        |  
-------------------------------------+--------------------------------------
Changes (by andy):

  * status:  new => closed
  * haspatch:  => 0
  * resolution:  => fixed


Comment:

 On wake you can figure out the wake source generally from here:

 # cat /sys/bus/platform/devices/neo1973-resume.0/resume_reason
   EINT00_ACCEL1
   EINT01_GSM
   EINT02_BLUETOOTH
   EINT03_DEBUGBRD
   EINT04_JACK
   EINT05_WLAN
   EINT06_AUXKEY
   EINT07_HOLDKEY
   EINT08_ACCEL2
 * EINT09_PMU
   EINT10_NULL
   EINT11_NULL
   EINT12_GLAMO
   EINT13_NULL
   EINT14_NULL
   EINT15_NULL

 and in the event of it being the PMU interrupt, which is the case for RTC
 alarm, you can get more info from here:

 # cat /sys/class/i2c-adapter/i2c-0/0-0073/resume_reason
 4000000000

 That bit shown above should be set on RTC alarm wake.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/81#comment:9>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac