summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorBin Meng <bmeng.cn@gmail.com>2015-10-11 21:37:45 -0700
committerSimon Glass <sjg@chromium.org>2015-10-21 07:46:27 -0600
commit74e56d19534f85a0f7d3c84f6d692534f2e1d9b5 (patch)
treef1256ae713ee0d44a6367be08667bae5c187f1b5 /arch
parent638a05894169b07ea8f6d21b6925ca353ea6ebb7 (diff)
downloadu-boot-imx-74e56d19534f85a0f7d3c84f6d692534f2e1d9b5.zip
u-boot-imx-74e56d19534f85a0f7d3c84f6d692534f2e1d9b5.tar.gz
u-boot-imx-74e56d19534f85a0f7d3c84f6d692534f2e1d9b5.tar.bz2
x86: baytrail: Issue full system reset in reset_cpu()
With MRC cache enabled, when typing 'reset' in the U-Boot shell, BayTrail FSP initialization hangs at "Configuring Memory Start": Setting BootMode to 0 Install PPI: 1F4C6F90-B06B-48D8-A201-BAE5F1CD7D56 Register PPI Notify: F894643D-C449-42D1-8EA8-85BDD8C65BDE About to call MrcInit(); BayleyBay Platform Type CurrentMrcData.BootMode = 4 Taking Fastboot path! Configuring Memory Start... Changing reset_cpu() to do a full system reset fixes this issue. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Acked-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'arch')
-rw-r--r--arch/x86/cpu/baytrail/valleyview.c6
1 files changed, 6 insertions, 0 deletions
diff --git a/arch/x86/cpu/baytrail/valleyview.c b/arch/x86/cpu/baytrail/valleyview.c
index 215e0d0..a009c14 100644
--- a/arch/x86/cpu/baytrail/valleyview.c
+++ b/arch/x86/cpu/baytrail/valleyview.c
@@ -65,3 +65,9 @@ int reserve_arch(void)
#endif
}
#endif
+
+void reset_cpu(ulong addr)
+{
+ /* cold reset */
+ x86_full_reset();
+}