summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexandru M Stan <amstan@chromium.org>2018-07-13 17:41:43 -0700
committerChromeOS Commit Bot <chromeos-commit-bot@chromium.org>2018-07-16 18:25:42 +0000
commita7ad347585dd305ea55e6a0d7f8fd97f58ebfb33 (patch)
tree5ac0044aac889ba2df33df42314d2d4228890f14
parent023f4602e86ed9fb7e108287e65c978649005c98 (diff)
downloadchrome-ec-a7ad347585dd305ea55e6a0d7f8fd97f58ebfb33.tar.gz
scarlet: Change FIFO settings
Similar to CL:1134494 Reduce the amount of datum to trigger a FIFO interruption. To improve timestamping in the kernel, we need to send a continuous stream of data to the host. In case of CTS batch test, we may not send anything for x100ms; the filter will not have any data to estimate the drift and may output invalid timestamps. Change the FIFO threshold to try to have more than ~10 samples in a singe batch. We still need a long FIFO when the EC is busy and can not process events from the sensor. BUG=b:73551961 BRANCH=scarlet TEST=in CtsHardwareTestCases, tests SensorBatchingTests pass more reliably. Change-Id: I254230498fcf270dfa303cf5eacec5d8abdd1225 Signed-off-by: Gwendal Grignou <gwendal@chromium.org> Signed-off-by: Alexandru M Stan <amstan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1137454 Reviewed-by: Philip Chen <philipchen@chromium.org>
-rw-r--r--board/scarlet/board.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/board/scarlet/board.h b/board/scarlet/board.h
index 2d562a9787..a6120be824 100644
--- a/board/scarlet/board.h
+++ b/board/scarlet/board.h
@@ -99,7 +99,7 @@
/* FIFO size is in power of 2. */
#define CONFIG_ACCEL_FIFO 256
-#define CONFIG_ACCEL_FIFO_THRES (CONFIG_ACCEL_FIFO / 3)
+#define CONFIG_ACCEL_FIFO_THRES 10
/* USB PD config */
#define CONFIG_CHARGE_MANAGER