summaryrefslogtreecommitdiff
path: root/arch/x86/cpu/baytrail
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2017-06-01 10:41:13 (GMT)
committerBin Meng <bmeng.cn@gmail.com>2017-06-05 00:55:22 (GMT)
commit37d1023264e7b73b72e0c42fd55de91c7018135d (patch)
treed123912fddd1b0c6dab6072c78288eb3a2883a50 /arch/x86/cpu/baytrail
parentf8f291b0962c795fcb025338d5c2284e2357a669 (diff)
downloadu-boot-37d1023264e7b73b72e0c42fd55de91c7018135d.tar.xz
x86: baytrail: Fix boot hang with a debug build
It was observed that when -DDEBUG is used to generate a debug build, U-Boot does not boot on MinnowMax board. A workaround is to disable CONFIG_DEBUG_UART. The real issue is that in order to have the debug uart to work, BayTrail SoC needs to be configured so that its internal uart is available to be used as the debug uart. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Stefan Roese <sr@denx.de> Reviewed-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch/x86/cpu/baytrail')
-rw-r--r--arch/x86/cpu/baytrail/Kconfig4
-rw-r--r--arch/x86/cpu/baytrail/early_uart.c5
2 files changed, 9 insertions, 0 deletions
diff --git a/arch/x86/cpu/baytrail/Kconfig b/arch/x86/cpu/baytrail/Kconfig
index 1c8ac37..6c85186 100644
--- a/arch/x86/cpu/baytrail/Kconfig
+++ b/arch/x86/cpu/baytrail/Kconfig
@@ -17,4 +17,8 @@ config INTERNAL_UART
reason, it is recommended that the UART port be used for
debug purposes only, eg: U-Boot console.
+config DEBUG_UART
+ bool
+ select DEBUG_UART_BOARD_INIT
+
endif
diff --git a/arch/x86/cpu/baytrail/early_uart.c b/arch/x86/cpu/baytrail/early_uart.c
index 471d592..afab21f 100644
--- a/arch/x86/cpu/baytrail/early_uart.c
+++ b/arch/x86/cpu/baytrail/early_uart.c
@@ -80,3 +80,8 @@ int setup_internal_uart(int enable)
return 0;
}
+
+void board_debug_uart_init(void)
+{
+ setup_internal_uart(1);
+}