commit 62569ecf526c7c01cb68ea461c6bbd3cb26057d2
author Mathias Agopian <mathias@google.com> Mon Nov 07 21:21:47 2011 -0800
committer Mathias Agopian <mathias@google.com> Wed Jun 27 17:07:56 2012 -0700
tree 2e7cd59d71c0d6ce30129dee9643d3f890d5601f
parent ae09d65f5b35cb51da2e1386a6dd7a52085f1325

SensorService now always clamps the requested rate

Requested rate will be clamped to the minimum rate and then
to 1ms. Previously we would return an error if a lower
rate was asked. The SensorManager documentation wording
allows this change.

We do this to get more consistancy between all the sensor
drivers / HALs

Change-Id: I199f76486fb76ccbb11e7280460a03726c767e84

services/sensorservice/SensorService.cpp

diff --git a/services/sensorservice/SensorService.cpp b/services/sensorservice/SensorService.cpp
index 11adbe2..7d5a761 100644
--- a/services/sensorservice/SensorService.cpp
+++ b/services/sensorservice/SensorService.cpp
@@ -478,8 +478,9 @@
     if (ns < 0)
         return BAD_VALUE;
 
-    if (ns == 0) {
-        ns = sensor->getSensor().getMinDelayNs();
+    nsecs_t minDelayNs = sensor->getSensor().getMinDelayNs();
+    if (ns < minDelayNs) {
+        ns = minDelayNs;
     }
 
     if (ns < MINIMUM_EVENTS_PERIOD)