[IMU_CAL] Don't dynamically change gyro latency
Toggling the latency request for gyro based on whether the sensor is
enabled or not does not have functional benefit (i.e. the latency
request while the sensor is disabled has no effect). Leaving it in the
"high-performance" state adds additional robustness against a possible
feedback loop between changing gyro sampling status due to other
clients' requests and IMU cal updating it own request.
Bug: 63844556
Test: use extra logging to confirm that IMU cal makes the expected
requests
Change-Id: I1332244c98edca4d75db753c790cdbe1127891d1
diff --git a/apps/imu_cal/imu_cal.cc b/apps/imu_cal/imu_cal.cc
index c30b672..abaca97 100644
--- a/apps/imu_cal/imu_cal.cc
+++ b/apps/imu_cal/imu_cal.cc
@@ -81,7 +81,7 @@
.enable = true,
.interval = Milliseconds(10).toRawNanoseconds(),
.highPerformanceLatency = kDefaultHighPerformanceLatency,
- .standByLatency = kDefaultStandByLatency,
+ .standByLatency = kDefaultHighPerformanceLatency,
},
[SENSOR_INDEX_MAG] = {
.type = CHRE_SENSOR_TYPE_UNCALIBRATED_GEOMAGNETIC_FIELD,
