diff options
author | Subrata Banik <subrata.banik@intel.com> | 2015-09-28 15:12:08 +0530 |
---|---|---|
committer | Martin Roth <martinroth@google.com> | 2016-01-17 22:52:02 +0100 |
commit | df13c31ed6fdad2cdb6e8e874f26e5cad2ce935f (patch) | |
tree | 858935bc9d8135a7a5fd118136b8850359371b64 /src/soc/intel/skylake | |
parent | e28846a0e89bfed307d792f8f5f128f5914a91fc (diff) |
intel/skylake: During RO mode after FSP reset CB lose original state
CB used to clear recovery status towards romstage end after FSP
memory init. Later inside FSP silicon init due to HSIO CRC mismatch
it will request for an additional reset.On next boot system resume
in dev mode rather than recovery because lost its original state
due to FSP silicon init reset.
Hence an additional 1 reset require to identify original state.
With this patch, we will get future platform reset info during romstage
and restore back recovery request flag so, in next boot CB can maintain
its original status and avoid 1 extra reboot.
BUG=chrome-os-partner:43517
BRANCH=none
TEST= build and booted Kunimitsu and tested RO mode
Change-Id: Ibf86ff2b140cd9ad259eb39987d78177535cd975
Signed-off-by: Patrick Georgi <pgeorgi@chromium.org>
Original-Commit-Id: 40ddc21a97b318510116b7d5c4314380778a40f7
Original-Change-Id: Ia52835f87ef580317e91931aee5dd0119dea8111
Original-Signed-off-by: Subrata Banik <subrata.banik@intel.com>
Original-Reviewed-on: https://chromium-review.googlesource.com/302257
Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Reviewed-on: https://review.coreboot.org/12975
Tested-by: build bot (Jenkins)
Reviewed-by: Martin Roth <martinroth@google.com>
Diffstat (limited to 'src/soc/intel/skylake')
-rw-r--r-- | src/soc/intel/skylake/Makefile.inc | 1 | ||||
-rw-r--r-- | src/soc/intel/skylake/fsp_reset.c | 62 |
2 files changed, 63 insertions, 0 deletions
diff --git a/src/soc/intel/skylake/Makefile.inc b/src/soc/intel/skylake/Makefile.inc index d6c2212310..9c578c56c1 100644 --- a/src/soc/intel/skylake/Makefile.inc +++ b/src/soc/intel/skylake/Makefile.inc @@ -37,6 +37,7 @@ ramstage-y += cpu_info.c ramstage-y += elog.c ramstage-y += finalize.c ramstage-y += flash_controller.c +ramstage-$(CONFIG_VBOOT_VERIFY_FIRMWARE) += fsp_reset.c ramstage-y += gpio.c ramstage-y += igd.c ramstage-y += lpc.c diff --git a/src/soc/intel/skylake/fsp_reset.c b/src/soc/intel/skylake/fsp_reset.c new file mode 100644 index 0000000000..4751872a47 --- /dev/null +++ b/src/soc/intel/skylake/fsp_reset.c @@ -0,0 +1,62 @@ +/* + * This file is part of the coreboot project. + * + * Copyright (C) 2015 Intel Corporation. + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU General Public License as published by + * the Free Software Foundation; version 2 of the License. + * + * This program is distributed in the hope that it will be useful, + * but WITHOUT ANY WARRANTY; without even the implied warranty of + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the + * GNU General Public License for more details. + */ +#include <bootstate.h> +#include <vendorcode/google/chromeos/vboot_handoff.h> + +static int is_recovery; /* flag to identify recovery mode */ + +/* + * coreboot used to clear recovery status towards romstage end after FSP + * memory init. Later inside FSP silicon init due to HSIO CRC mismatch + * or other silicon related programming may request for an additional + * reset. Thus on the next boot the system resumed in normal mode rather than + * recovery because it lost its original state due to FSP silicon init reset. + * Hence it needs an addition reset to get into old state and continue + * booting into recovery mode. This function will set recovery reason + * during Silicon init, in case of recovery mode booting, + * so, system will not lose its original context. + */ +static void set_recovery_request(void *unused) +{ + is_recovery = recovery_mode_enabled(); + /* + * Set recovery flag during Recovery Mode Silicon Init + * & store recovery request into VBNV + */ + if (is_recovery) + set_recovery_mode_into_vbnv(vboot_recovery_reason()); + +} + +static void clear_recovery_request(void *unused) +{ + /* + * Done with Silicon Init, it's safe to clear + * reset request now with assumption that no reset occurs hereafter + * so we will not miss original data. + */ + if (is_recovery) + set_recovery_mode_into_vbnv(0); +} +/* + * On Recovery Path Set Recovery Request during early RAMSTAGE + * before initiated Silicon Init + */ +BOOT_STATE_INIT_ENTRY(BS_PRE_DEVICE, BS_ON_ENTRY, set_recovery_request, NULL); +/* + * On Recovery Path Clear Recovery Request during early RAMSTAGE + * end of Silicon Init + */ +BOOT_STATE_INIT_ENTRY(BS_DEV_INIT_CHIPS, BS_ON_EXIT, clear_recovery_request, NULL); |