summaryrefslogtreecommitdiff
path: root/board/poppy/board.h
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@google.com>2018-03-23 22:36:35 -0700
committerchrome-bot <chrome-bot@chromium.org>2018-03-26 02:07:24 -0700
commit5c611cedbfcff0c2fed25462b0477efcff014c36 (patch)
treefe76311777d0bb1b59a3926a191b4d1d911eb795 /board/poppy/board.h
parent245b494e145d6a928aa277670432d396862698f9 (diff)
downloadchrome-ec-5c611cedbfcff0c2fed25462b0477efcff014c36.tar.gz
Add config for boards that cannot distinguish reset type
We have a growing list of boards in chip/npcx/system.c that are unable to distinguish a reset from a power-on or a reset-pin type. Instead of being a temporary issue this is now solidified in the design on some kabylake boards. Instead of defining board-specific checks in the chip code this change adds a config option that the relevant boards can define. BUG=b:76232539 BRANCH=none TEST=make -j buildall passes Change-Id: I76e0f011d70ce6f778b1fb6a56c2779c39c3cbd6 Signed-off-by: Duncan Laurie <dlaurie@google.com> Reviewed-on: https://chromium-review.googlesource.com/979575 Reviewed-by: Furquan Shaikh <furquan@chromium.org>
Diffstat (limited to 'board/poppy/board.h')
-rw-r--r--board/poppy/board.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/board/poppy/board.h b/board/poppy/board.h
index 950728a7ac..d865890b11 100644
--- a/board/poppy/board.h
+++ b/board/poppy/board.h
@@ -19,6 +19,7 @@
#define CONFIG_BACKLIGHT_LID
#define CONFIG_BOARD_VERSION
#define CONFIG_BOARD_SPECIFIC_VERSION
+#define CONFIG_BOARD_FORCE_RESET_PIN
#define CONFIG_BUTTON_TRIGGERED_RECOVERY
#define CONFIG_DPTF
#define CONFIG_DPTF_DEVICE_ORIENTATION