Lines Matching refs:events

58      * After sensor de-activation, existing sensor events that have not
60      * subsequent activations do not get stale sensor events (events
74      * framework of asynchronous events, such as a dynamic sensor connection.
76      * The Event FMQ is used to transport sensor events from the HAL to the
80      * sensor events, the HAL writes the sensor events to the Event FMQ.
82      * Once the HAL is finished writing sensor events to the Event FMQ, the HAL
83      * must notify the framework that sensor events are available to be read and
92      * be notified and unblocked when the framework has successfully read events
96      * safe to release its wake_lock. When the framework receives WAKE_UP events
98      * framework must write the number of WAKE_UP events processed to the Wake
100      * decrements its current count of unprocessed WAKE_UP events and releases
101      * its wake_lock if the current count of unprocessed WAKE_UP events is
104      * events _before_ posting the event to the Wake Lock FMQ, in order to avoid
113      * asynchronous events, such as a dynamic sensor connection.
115      * The name of any wake_lock acquired by the Sensors HAL for WAKE_UP events
120      * Wake Lock FMQ, then any held wake_lock for WAKE_UP events must be
126      * number of outstanding WAKE_UP events should also be reset to zero, and
127      * any outstanding wake_locks held as a result of WAKE_UP events should be
138      *     create the Event FMQ which is where sensor events are written. The
140      *     sensor events.
142      *     create the Wake Lock FMQ which is where wake_lock events are read
144      *     used to write wake_lock events.
163      * lost events, nor can transitioning from a high maximum report latency to
205      * injecting sensor events.
208      * type events should not be routed back to the sensor event queue.