Lines Matching refs:to
10 * Unless required by applicable law or agreed to in writing, software
32 * from the initial call to getSensorsList after a device boot until the
34 * between subsequent calls to getSensorsList, even across restarts of the
59 * been written to the event queue must be abandoned immediately so that
61 * that are generated prior to the latter activation).
63 * @param sensorHandle is the handle of the sensor to change.
64 * @param enabled set to true to enable, or false to disable the sensor.
72 * The Fast Message Queues (FMQ) that are used to send data between the
73 * framework and the HAL. The callback is used by the HAL to notify the
76 * The Event FMQ is used to transport sensor events from the HAL to the
78 * Data may only be written to the Event FMQ. Data must not be read from
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
88 * function to EventQueueFlagBits::READ_AND_PROCESS.
91 * notification must be set to EventQueueFlagBits::EVENTS_READ in order to
95 * The Wake Lock FMQ is used by the framework to notify the HAL when it is
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
102 * zero. It is important to note that the HAL must acquire the wake lock and
104 * events _before_ posting the event to the Wake Lock FMQ, in order to avoid
105 * a race condition that can lead to loss of wake lock synchronization with
108 * The framework must use the WakeLockQueueFlagBits::DATA_WRITTEN value to
109 * notify the HAL that data has been written to the Wake Lock FMQ and must
112 * The ISensorsCallback is used by the HAL to notify the framework of
119 * event was written to the Event FMQ without receiving a message on the
125 * new descriptors must be used to create new FMQs within the HAL. The
126 * number of outstanding WAKE_UP events should also be reset to zero, and
131 * properly cleaned up when initialize is called in order to ensure that the
135 * to initialize from simultaneously modifying state.
137 * @param eventQueueDescriptor Fast Message Queue descriptor that is used to
139 * descriptor is obtained from the framework's FMQ that is used to read
141 * @param wakeLockDescriptor Fast Message Queue descriptor that is used to
144 * used to write wake_lock events.
161 * activated, in which case it must not cause any sensor measurements to
162 * be lost: transitioning from one sampling rate to the other cannot cause
163 * lost events, nor can transitioning from a high maximum report latency to
166 * @param sensorHandle handle of sensor to be changed.
169 * to time of report.
181 * Flush adds a FLUSH_COMPLETE metadata event to the end of the "batch mode"
184 * SUCCESS and add a trivial FLUSH_COMPLETE event added to the event stream.
185 * This applies to all sensors other than one-shot sensors. If the sensor
190 * @param sensorHandle handle of sensor to be flushed.
196 * Inject a single sensor event or push operation environment parameters to
199 * When device is in NORMAL mode, this function is called to push operation
200 * environment data to device. In this operation, Event is always of
208 * type events should not be routed back to the sensor event queue.
212 * @param event sensor event to be injected
224 * content to initial value (depending on memory format settings).
245 * @param channelHandle handle of direct channel to be unregistered.
257 * @param sensorHandle handle of sensor to be configured. When combined
258 * with STOP rate, sensorHandle can be -1 to denote all active sensors
260 * @param channelHandle handle of direct channel to be configured.
265 * @return reportToken positive integer to identify multiple sensors of