#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:               
----------------------+-----------------------------------------------------
Changes (by dsaxena):

 * cc: cosmicpenguin (added)


Comment:

 Replying to [comment:2 cjb]:
 > We do have a working /dev/rtc0 at the moment, though read() seems to be
 hanging on it after resume.

 Did you open with O_NONBLOCK? It shouldn't hang it that case but just
 return 0 if an alarm did not happen. If you're programming an alarm and it
 is not triggering, then something else
 is going on.

 Jordan, if we get woken up by RTC, will we still receive the RTC
 interrupt?

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