Lines Matching full:flp
29 * The software implementation of FLP will decide when to use
42 #define FUSED_LOCATION_HARDWARE_MODULE_ID "flp"
45 * Name for the FLP location interface
50 * Name for the FLP location interface
76 * APIs. Batching is mandatory when FLP implementation
168 * This can be used to prevent the CPU from suspending while handling FLP events.
173 * Callback utility for releasing the FLP wakelock.
186 /** FLP callback structure. */
197 /** Options with the batching FLP APIs */
242 * Represents the standard FLP interface.
355 * Get a handle to the FLP Interface.
366 * FLP diagnostic callback structure.
391 * Injects diagnostic data into the FLP subsystem.
399 * All these settings shall be injected to FLP HAL at FLP init time.
424 * Injects debug data into the FLP subsystem.
463 * circle reported by the FLP subsystem. Now with regard to "b", the system is
471 * FLP subsystem isn't confident enough that the user is either inside or
476 * transitions, when the FLP system is confident that the user has entered
487 * and then we get an accurate FLP location fix, it needs to trigger the
491 * When the FLP system is unavailable, flp_geofence_status_callback should be
508 * location - The current location as determined by the FLP subsystem.
528 * monitoring by the FLP sub-system For example, if the GPS system determines that it cannot
