Lines Matching refs:is
11 * distributed under the License is distributed on an "AS IS" BASIS,
46 * Data is injected for the supported sensors by the sensor service in
50 * BAD_VALUE if requested mode is not supported
51 * PERMISSION_DENIED if operation is not allowed
63 * @param sensorHandle is the handle of the sensor to change.
65 * @return result OK on success, BAD_VALUE if sensorHandle is invalid.
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
77 * framework. The Event FMQ is created using the eventQueueDescriptor.
79 * the Event FMQ since the framework is the only reader. Upon receiving
82 * Once the HAL is finished writing sensor events to the Event FMQ, the HAL
84 * processed. This is accomplished by either:
90 * If the Event FMQ’s writeBlocking() function is used, the read
95 * The Wake Lock FMQ is used by the framework to notify the HAL when it is
101 * its wake_lock if the current count of unprocessed WAKE_UP events is
102 * zero. It is important to note that the HAL must acquire the wake lock and
112 * The ISensorsCallback is used by the HAL to notify the framework of
123 * If either the Event FMQ or the Wake Lock FMQ is already initialized when
124 * initialize is invoked, then both existing FMQs must be discarded and the
131 * properly cleaned up when initialize is called in order to ensure that the
132 * HAL and framework's state is consistent (e.g. after a runtime restart).
137 * @param eventQueueDescriptor Fast Message Queue descriptor that is used to
138 * create the Event FMQ which is where sensor events are written. The
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
142 * create the Wake Lock FMQ which is where wake_lock events are read
143 * from. The descriptor is obtained from the framework's FMQ that is
147 * @return result OK on success; BAD_VALUE if descriptor is invalid (such
160 * report latency. This function can be called while the sensor is
168 * @param maxReportLatencyNs allowed delay time before an event is sampled
182 * FIFO for the specified sensor and flushes the FIFO. If the FIFO is empty
186 * is a one-shot sensor, flush must return BAD_VALUE and not generate any
187 * flush complete metadata. If the sensor is not active at the time flush()
188 * is called, flush() return BAD_VALUE.
191 * @return result OK on success and BAD_VALUE if sensorHandle is invalid.
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
204 * When device is in DATA_INJECTION mode, this function is also used for
213 * @return result OK on success; PERMISSION_DENIED if operation is not
214 * allowed; INVALID_OPERATION, if this functionality is unsupported;
223 * return, the sensor hardware is responsible for resetting the memory
227 * @return result OK on success; BAD_VALUE if shared memory information is
229 * system; INVALID_OPERATION if functionality is not supported.
232 * unregisterDirectChannel if result is OK, -1 otherwise.
246 * @return result OK if direct report is supported; INVALID_OPERATION
262 * @return result OK on success; BAD_VALUE if parameter is invalid (such as
263 * rate level is not supported by sensor, channelHandle does not exist,
264 * etc); INVALID_OPERATION if functionality is not supported.
266 * the same type in a single direct channel. Ignored if rate is STOP.