AMD k8 fam10: Drop excessive spinlock initialization
If CAR migration operations unintentionally set the lock, BSP would have got stuck on printk() calls above already. Change-Id: I35155ebcb00475a0964fc639ee74ad2755127740 Signed-off-by: Kyösti Mälkki <kyosti.malkki@gmail.com> Reviewed-on: https://review.coreboot.org/15589 Tested-by: build bot (Jenkins) Reviewed-by: Aaron Durbin <adurbin@chromium.org> Tested-by: Raptor Engineering Automated Test Stand <noreply@raptorengineeringinc.com>
This commit is contained in:
parent
b5664de76d
commit
70cd54310b
|
@ -94,13 +94,6 @@ static void prepare_ramstage_region(int s3resume)
|
|||
memset_((void*)0, 0, CONFIG_RAMTOP - backup_top);
|
||||
}
|
||||
|
||||
#if IS_ENABLED(CONFIG_HAVE_ROMSTAGE_CONSOLE_SPINLOCK)
|
||||
initialize_romstage_console_lock();
|
||||
#endif
|
||||
#if IS_ENABLED(CONFIG_HAVE_ROMSTAGE_NVRAM_CBFS_SPINLOCK)
|
||||
initialize_romstage_nvram_cbfs_lock();
|
||||
#endif
|
||||
|
||||
print_car_debug(" Done\n");
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue