#6670 HIGH 12.1.0: Userspace power manager needs to know about the audio device state

[Zarro Boogs per Child]

#6670: Userspace power manager needs to know about the audio device state
---------------------------------+------------------------------------------
           Reporter:  cjb        |       Owner:  pgf                               
               Type:  defect     |      Status:  new                               
           Priority:  high       |   Milestone:  12.1.0                            
          Component:  kernel     |     Version:  Development source as of this date
         Resolution:             |    Keywords:                                    
        Next_action:  never set  |    Verified:  0                                 
Deployment_affected:             |   Blockedby:                                    
           Blocking:             |  
---------------------------------+------------------------------------------

Comment(by sascha_silbe):

 As Paul pointed out correctly on the mailing list (or maybe IRC), simply
 reading the current status of the audio device is just a point-in-time
 check. inotify doesn't notice changes to the status file either. So in
 theory we're opening ourselves up for a race condition. However, it would
 be a problem even with a better check: AFAICT using the audio device
 doesn't increment wakeup_count, so if an Activity started using the audio
 device right before we suspend, we'd have the same problem.

 In practice, it will probably be less of a problem, as most usage of audio
 devices is going to be the direct result of some external event (user
 input or network traffic).

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