| Message ID | 20200708033246.2626378-17-sjg@chromium.org |
|---|---|
| State | Accepted |
| Commit | efd31328525629db9fc8b48f1e5b33f8ee1de4d7 |
| Headers | show |
| Series | x86: Programmatic generation of ACPI tables (Part C) | expand |
On Wed, Jul 8, 2020 at 11:34 AM Simon Glass <sjg at chromium.org> wrote: > > If there is MRC information we should run FSP-M with a different > boot_mode flag since it is supposed to do a 'fast path' through the > memory init. Fix this. > > Signed-off-by: Simon Glass <sjg at chromium.org> > Reviewed-by: Wolfgang Wallner <wolfgang.wallner at br-automation.com> > --- > > Changes in v2: > - Add a new commit to handle the boot_mode fix > > arch/x86/cpu/apollolake/fsp_m.c | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) > Reviewed-by: Bin Meng <bmeng.cn at gmail.com>
diff --git a/arch/x86/cpu/apollolake/fsp_m.c b/arch/x86/cpu/apollolake/fsp_m.c index 65461d85b8..e19a2b0826 100644 --- a/arch/x86/cpu/apollolake/fsp_m.c +++ b/arch/x86/cpu/apollolake/fsp_m.c @@ -26,7 +26,8 @@ int fspm_update_config(struct udevice *dev, struct fspm_upd *upd) return log_msg_ret("mrc", cache_ret); arch->stack_base = (void *)0xfef96000; arch->boot_loader_tolum_size = 0; - arch->boot_mode = FSP_BOOT_WITH_FULL_CONFIGURATION; + arch->boot_mode = cache_ret ? FSP_BOOT_WITH_FULL_CONFIGURATION : + FSP_BOOT_ASSUMING_NO_CONFIGURATION_CHANGES; node = dev_ofnode(dev); if (!ofnode_valid(node))