summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexandru M Stan <amstan@chromium.org>2018-07-13 17:41:43 -0700
committerchrome-bot <chrome-bot@chromium.org>2018-07-16 16:32:38 -0700
commitd4e075c3c1bc6faf34677941295266f5e7d07e12 (patch)
tree6093b5cd9c51382b1faef81df80bae153da947a1
parenta617511224e71fd084d10b869dd17922558b15fd (diff)
downloadchrome-ec-d4e075c3c1bc6faf34677941295266f5e7d07e12.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/1137474 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 a3c9683c7c..e5ef795008 100644
--- a/board/scarlet/board.h
+++ b/board/scarlet/board.h
@@ -100,7 +100,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