summaryrefslogtreecommitdiff
path: root/board/google/chromebook_link/Kconfig
diff options
context:
space:
mode:
authorSimon Glass <sjg@chromium.org>2014-11-12 22:42:09 -0700
committerSimon Glass <sjg@chromium.org>2014-11-21 07:34:11 +0100
commitd1cd045982b1e1e4db2c1cc2b2b932f739b78a11 (patch)
tree042be9d3ac848c6799756f5e7fc6c1a6391d1d2a /board/google/chromebook_link/Kconfig
parentfce7b2768364366bd4c4af9188186f6b3f9c2fe8 (diff)
downloadu-boot-imx-d1cd045982b1e1e4db2c1cc2b2b932f739b78a11.zip
u-boot-imx-d1cd045982b1e1e4db2c1cc2b2b932f739b78a11.tar.gz
u-boot-imx-d1cd045982b1e1e4db2c1cc2b2b932f739b78a11.tar.bz2
x86: Emit post codes in startup code for Chromebooks
On x86 it is common to use 'post codes' which are 8-bit hex values emitted from the code and visible to the user. Traditionally two 7-segment displays were made available on the motherboard to show the last post code that was emitted. This allows diagnosis of a boot problem since it is possible to see where the code got to before it died. On modern hardware these codes are not normally visible. On Chromebooks they are displayed by the Embedded Controller (EC), so it is useful to emit them. We must enable this feature for the EC to see the codes, so add an option for this. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
Diffstat (limited to 'board/google/chromebook_link/Kconfig')
-rw-r--r--board/google/chromebook_link/Kconfig4
1 files changed, 4 insertions, 0 deletions
diff --git a/board/google/chromebook_link/Kconfig b/board/google/chromebook_link/Kconfig
index 975d557..9c715ba 100644
--- a/board/google/chromebook_link/Kconfig
+++ b/board/google/chromebook_link/Kconfig
@@ -12,4 +12,8 @@ config SYS_SOC
config SYS_CONFIG_NAME
default "chromebook_link"
+config EARLY_POST_CROS_EC
+ bool "Enable early post to Chrome OS EC"
+ default y
+
endif