diff options
| author | Enrico Granata <egranata@chromium.org> | 2019-03-14 17:07:45 -0700 |
|---|---|---|
| committer | chrome-bot <chrome-bot@chromium.org> | 2019-03-26 04:43:12 -0700 |
| commit | 45bb97a58126aa943412c343bc4847e972d3b707 (patch) | |
| tree | c34ce3417f975ab9efa81534194bbd29422d4f98 /board/rammus | |
| parent | 184410c9ee7530404813f5bd0a80a0a9d21f2a5a (diff) | |
| download | chrome-ec-45bb97a58126aa943412c343bc4847e972d3b707.tar.gz | |
rammus: Disable tight timestamps
Rammus 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
BRANCH=rammus
TEST=tight_timestamps is 0, ran CtsSensorTestCases
Change-Id: I459f2673abad7ff75ba9e8a844b7702dee1ef8c0
Signed-off-by: Enrico Granata <egranata@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1524667
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Alexandru M Stan <amstan@chromium.org>
Diffstat (limited to 'board/rammus')
| -rw-r--r-- | board/rammus/board.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/board/rammus/board.h b/board/rammus/board.h index 66c79f9317..eb6df68f75 100644 --- a/board/rammus/board.h +++ b/board/rammus/board.h @@ -120,6 +120,8 @@ #define CONFIG_LID_ANGLE_SENSOR_LID LID_ACCEL #define CONFIG_LID_ANGLE_UPDATE +#undef CONFIG_SENSOR_TIGHT_TIMESTAMPS + /* FIFO size is in power of 2. */ #define CONFIG_ACCEL_FIFO 512 |