#8843 HIGH 9.1.0: Tell userspace whether an RTC alarm woke us up.

[Zarro Boogs per Child]

#8843: Tell userspace whether an RTC alarm woke us up.
----------------------+-----------------------------------------------------
   Reporter:  cjb     |       Owner:  dsaxena      
       Type:  defect  |      Status:  new          
   Priority:  high    |   Milestone:  9.1.0        
  Component:  kernel  |     Version:  not specified
 Resolution:          |    Keywords:               
Next_action:  review  |    Verified:  0            
  Blockedby:          |    Blocking:               
----------------------+-----------------------------------------------------

Comment(by dsaxena):

 I'd really like to put a moratorium on adding new fields to /sys/power/
 until we get the interfaces vetted upstream. If we're going to program the
 RTC, need to write a driver for the southbridge chip and the driver
 interface provides a method to read alarm IRQ status. See
 Documentation/rtc.txt in the kernel sources. I think what we can do is
 open() the rtc dev with O_NONBLOCK and when we wakeup, call read() to see
 if we received an alarm IRQ (!0 data). If not, we ioctl() to turn off the
 alarm interrupt and then go read /sys/power/wakeup_source to find the real
 wakeup event.

-- 
Ticket URL: <http://dev.laptop.org/ticket/8843#comment:1>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system