driver: bmi160: Improve FIFO handling

- Add 3ms after write, found issue with SPI writes.
- Do not check FIFO if all sensors are disabled.
It contains garbage (0x848484....)
- Do not check FIFO length. It can be 0 even if there
is data in the fifo.
- Remove forever latch and do not reset Interrupt in the handler,
we are using level interrupt.
- Flush and exit when the FIFO is in a bad state.

BRANCH=smaug
BUG=chrome-os-partner:43339,chrome-os-partner:39900
TEST=Ran CTS tests. Check sensor is stable.

Change-Id: I5cbae819e780b4d50d02829fd8e1178cf34c3f84
Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/289839
Reviewed-by: Vincent Palatin <vpalatin@chromium.org>

1 files changed, 2 insertions, 0 deletions

diff --git a/driver/accelgyro_bmi160.h b/driver/accelgyro_bmi160.h
index 27df9c2c1f..4101b1f07e 100644
--- a/driver/accelgyro_bmi160.h
+++ b/driver/accelgyro_bmi160.h
@@ -382,6 +382,8 @@ enum bmi160_running_mode {
 };
 
 #define BMI160_FLAG_SEC_I2C_ENABLED    (1 << 0)
+#define BMI160_FIFO_FLAG_OFFSET        4
+#define BMI160_FIFO_ALL_MASK           7
 
 struct bmi160_drv_data_t {
 	struct motion_data_t saved_data[3];