ELOG: Don't disable SPI controller lockdown
Now that WREN prefix is handled properly ELOG is able to write when the SPI controller is locked down. To test, ensure that runtime SPI write via ELOG is successful by checking the event log for a kernel shutdown reason code: 5 | 2012-08-27 11:09:48 | Kernel Event | Clean Shutdown 6 | 2012-08-27 11:09:50 | System boot | 26 7 | 2012-08-27 11:09:50 | System Reset Change-Id: If6d0dced7cb0f5ca7038b3d758f31b856826d30b Signed-off-by: Duncan Laurie <dlaurie@chromium.org> Reviewed-on: http://review.coreboot.org/1712 Reviewed-by: Marc Jones <marcj303@gmail.com> Tested-by: build bot (Jenkins)
This commit is contained in:
parent
a2f1b95340
commit
f1c76ef605
|
@ -31,11 +31,8 @@ void intel_pch_finalize_smm(void)
|
||||||
RCBA32(0x3898) = SPI_OPMENU_LOWER;
|
RCBA32(0x3898) = SPI_OPMENU_LOWER;
|
||||||
RCBA32(0x389c) = SPI_OPMENU_UPPER;
|
RCBA32(0x389c) = SPI_OPMENU_UPPER;
|
||||||
|
|
||||||
/* Need to fix SMI driver use of opcode menu */
|
|
||||||
#if !CONFIG_ELOG_GSMI
|
|
||||||
/* Lock SPIBAR */
|
/* Lock SPIBAR */
|
||||||
RCBA32_OR(0x3804, (1 << 15));
|
RCBA32_OR(0x3804, (1 << 15));
|
||||||
#endif
|
|
||||||
|
|
||||||
/* TCLOCKDN: TC Lockdown */
|
/* TCLOCKDN: TC Lockdown */
|
||||||
RCBA32_OR(0x0050, (1 << 31));
|
RCBA32_OR(0x0050, (1 << 31));
|
||||||
|
|
Loading…
Reference in New Issue