intel/fsp1_1: Do not re-init TPM in romstage if already setup in verstage
For platforms that do verification of memory init (and have verstage execute before romstage) FSP should not attempt to re-initialize the TPM again in romstage as it has already been done. BUG=chrome-os-partner:50633 BRANCH=glados TEST=boot and resume on chell and ensure TPM is not re-initialized Change-Id: Ied6f39dc8dacdbc3d76070b6135de2308196ff53 Signed-off-by: Patrick Georgi <pgeorgi@chromium.org> Original-Commit-Id: fefd4d4b3fde4c7fe4b6de304790914b7a2f87d8 Original-Change-Id: I60a2e4e2d73270697218f094527e09d444e6ab56 Original-Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Original-Previous-Reviewed-on: https://chromium-review.googlesource.com/332433 Original-(cherry picked from commit 2de1fd57fe1db7960e0bb86c64dccf827fa55742) Original-Reviewed-on: https://chromium-review.googlesource.com/332299 Original-Reviewed-by: Aaron Durbin <adurbin@chromium.org> Reviewed-on: https://review.coreboot.org/14106 Tested-by: build bot (Jenkins) Reviewed-by: Martin Roth <martinroth@google.com>
This commit is contained in:
parent
92658db3ca
commit
fe4983e5aa
|
@ -173,8 +173,15 @@ void romstage_common(struct romstage_params *params)
|
||||||
hard_reset();
|
hard_reset();
|
||||||
}
|
}
|
||||||
|
|
||||||
if (IS_ENABLED(CONFIG_LPC_TPM))
|
/*
|
||||||
init_tpm(params->power_state->prev_sleep_state == SLEEP_STATE_S3);
|
* Initialize the TPM, unless the TPM was already initialized
|
||||||
|
* in verstage and used to verify romstage.
|
||||||
|
*/
|
||||||
|
if (IS_ENABLED(CONFIG_LPC_TPM) &&
|
||||||
|
!IS_ENABLED(CONFIG_RESUME_PATH_SAME_AS_BOOT) &&
|
||||||
|
!IS_ENABLED(CONFIG_VBOOT_STARTS_IN_BOOTBLOCK))
|
||||||
|
init_tpm(params->power_state->prev_sleep_state ==
|
||||||
|
SLEEP_STATE_S3);
|
||||||
}
|
}
|
||||||
|
|
||||||
void after_cache_as_ram_stage(void)
|
void after_cache_as_ram_stage(void)
|
||||||
|
|
Loading…
Reference in New Issue