diff options
| author | Gwendal Grignou <gwendal@chromium.org> | 2015-09-24 15:11:36 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2015-09-28 13:07:23 -0700 |
| commit | a0a1d18e06053b3cf2f390d31cd032560b184544 (patch) | |
| tree | 87fe044f65edb51a65cae61934f077bb92299d94 | |
| parent | 9d9f020aaf19267e767c48dcf96db1319e3669ce (diff) | |
| download | chrome-ec-a0a1d18e06053b3cf2f390d31cd032560b184544.tar.gz | |
common: motion: Fix error calculating oversampling.
cl:298688 was wrong and oversampling calculation, used to drop
events that AP does not want was incorrect.
We were comparing mHz with Hz.
BUG=b:24367625
BRANCH=smaug
TEST=Before, we would fail all
android.hardware.cts.SingleSensorTests#testAccelerometer tests where
frequency was lower than 100Hz. After, we pass thoses tests.
Change-Id: I487feb4e235a21f78d367397b5890ebcc5864b22
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/302176
Reviewed-by: Alec Berg <alecaberg@chromium.org>
| -rw-r--r-- | common/motion_sense.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/common/motion_sense.c b/common/motion_sense.c index f72748091a..f05e8e91b0 100644 --- a/common/motion_sense.c +++ b/common/motion_sense.c @@ -93,7 +93,7 @@ void motion_sense_fifo_add_unit(struct ec_response_motion_sensor_data *data, /* For valid sensors, check if AP really needs this data */ if (valid_data) { - int ap_odr = BASE_ODR(sensor->config[SENSOR_CONFIG_AP].odr); + fp_t ap_odr = fp_div(BASE_ODR(sensor->config[SENSOR_CONFIG_AP].odr), 1000); /* Use integer, conversion to FP will overflow */ fp_t rate = fp_div(sensor->drv->get_data_rate(sensor), 1000); |