summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEnrico Granata <egranata@chromium.org>2019-05-24 10:33:16 -0700
committerCommit Bot <commit-bot@chromium.org>2019-05-29 00:26:31 +0000
commit67ffa1b839b04cfee4bd62de2ffbda76cbbadd79 (patch)
tree451df53508b6aec8d2b813e4496188200fc78d17
parentfeadddbd783ec153f12009f65dbdacd0275d3eba (diff)
downloadchrome-ec-67ffa1b839b04cfee4bd62de2ffbda76cbbadd79.tar.gz
nami: Disable tight timestamps
Nami boards do not have a dedicated GPIO for MKBP events between EC and AP. On boards without this hardware support, the tight timestamps feature cannot be reliably supported due to issues with the performance of the ACPI SCI chain, compared to a dedicated interrupt. Disabling tight_timestamps restores legacy behavior that is known to fare better with sensors events over SCI. BUG=b:123700100,b:133433007 BRANCH=nami TEST=tight_timestamps is 0 testSensorTimeStamps passes 8/10 tries Change-Id: I4b5816eb09e635a3d167a4b8accefab1552a40c4 Signed-off-by: Enrico Granata <egranata@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1629315 Reviewed-by: Kazuhiro Inaba <kinaba@chromium.org> Reviewed-by: Gwendal Grignou <gwendal@chromium.org>
-rw-r--r--board/nami/board.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/board/nami/board.h b/board/nami/board.h
index 5ec59c24bf..41d6070317 100644
--- a/board/nami/board.h
+++ b/board/nami/board.h
@@ -150,6 +150,8 @@
/* KB backlight driver */
#define CONFIG_LED_DRIVER_LM3509
+#undef CONFIG_SENSOR_TIGHT_TIMESTAMPS
+
/* FIFO size is in power of 2. */
#define CONFIG_ACCEL_FIFO 512