soc/intel/fast_spi: Use smarter mtrr code in ramstage
mtrr_use_temp_range is a lot smarter than the plain set_var_mtrr. It will compute a new optimal solution with the temp ranges included while also taking care of the cleanup before loading the payload/s3 resume. Change-Id: I283ba07fc12c410be39dfdc828657598237247c1 Signed-off-by: Arthur Heymans <arthur@aheymans.xyz> Reviewed-on: https://review.coreboot.org/c/coreboot/+/63550 Reviewed-by: Subrata Banik <subratabanik@google.com> Reviewed-by: Lean Sheng Tan <sheng.tan@9elements.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
This commit is contained in:
parent
29aa1e1567
commit
481599f2c8
1 changed files with 5 additions and 0 deletions
|
@ -223,6 +223,11 @@ void fast_spi_set_strap_msg_data(uint32_t soft_reset_data)
|
|||
|
||||
static void fast_spi_enable_cache_range(unsigned int base, unsigned int size)
|
||||
{
|
||||
if (ENV_RAMSTAGE) {
|
||||
mtrr_use_temp_range(base, size, MTRR_TYPE_WRPROT);
|
||||
return;
|
||||
}
|
||||
|
||||
const int type = MTRR_TYPE_WRPROT;
|
||||
int mtrr = get_free_var_mtrr();
|
||||
if (mtrr == -1) {
|
||||
|
|
Loading…
Reference in a new issue