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-06-10 17:20:47 +0000
commit876e7e026d4c8898014d8efe4cd87fbf487bebe4 (patch)
tree6060ab3d121949d27ebb1958254b3d6a5ced6e60
parentdcde9078504e270e31a824dfd221045bd3cea31f (diff)
downloadchrome-ec-876e7e026d4c8898014d8efe4cd87fbf487bebe4.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> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1648956 Reviewed-by: Alexandru M Stan <amstan@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 34c3469bc5..16f4cb9521 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