summaryrefslogtreecommitdiff
path: root/include/config.h
diff options
context:
space:
mode:
authorDuncan Laurie <dlaurie@google.com>2018-03-23 22:36:35 -0700
committerChromeOS Commit Bot <chromeos-commit-bot@chromium.org>2018-03-27 18:22:48 +0000
commita659997e479755e7a9d0a723dbb24c5d19be41b4 (patch)
tree1d90c13e95b4d47ca7470d6475fb648214380794 /include/config.h
parentd22019b1d4c2d82f6cd4aaa17f88ba68ee1698d7 (diff)
downloadchrome-ec-a659997e479755e7a9d0a723dbb24c5d19be41b4.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=none 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> Reviewed-on: https://chromium-review.googlesource.com/982340 Commit-Queue: Furquan Shaikh <furquan@chromium.org> Tested-by: Furquan Shaikh <furquan@chromium.org> Trybot-Ready: Furquan Shaikh <furquan@chromium.org>
Diffstat (limited to 'include/config.h')
-rw-r--r--include/config.h6
1 files changed, 6 insertions, 0 deletions
diff --git a/include/config.h b/include/config.h
index c163ee5bb5..f96103a4af 100644
--- a/include/config.h
+++ b/include/config.h
@@ -420,6 +420,12 @@
/* EC responses to a board defined I2C slave address */
#undef CONFIG_BOARD_I2C_SLAVE_ADDR
+/*
+ * The board is unable to distinguish EC reset from power-on so it should treat
+ * all resets as triggered by RESET_PIN even if it is a POWER_ON reset.
+ */
+#undef CONFIG_BOARD_FORCE_RESET_PIN
+
/* Permanent LM4 boot configuration */
#undef CONFIG_BOOTCFG_VALUE