mb/google/rambi: Fix assumption that vboot runs after romstage
Now VBOOT is always assumed to run after romstage and be linked inside romstage. This currently is the case but for flexibility reasons (e.g. linking romstage into bootblock or having a verstage before romstage) this could be more precise. Signed-off-by: Arthur Heymans <arthur@aheymans.xyz> Change-Id: I361731c930a35e12245153920df1b6884d47064c Reviewed-on: https://review.coreboot.org/c/coreboot/+/78938 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Martin L Roth <gaumless@gmail.com>
This commit is contained in:
parent
e8ce421069
commit
ab5a9f9378
|
@ -31,7 +31,7 @@ int get_write_protect_state(void)
|
||||||
* there is a 10K pullup. Disable the internal pull in romstage so that
|
* there is a 10K pullup. Disable the internal pull in romstage so that
|
||||||
* there isn't any ambiguity in the reading.
|
* there isn't any ambiguity in the reading.
|
||||||
*/
|
*/
|
||||||
if (ENV_ROMSTAGE)
|
if (ENV_ROMSTAGE_OR_BEFORE)
|
||||||
ssus_disable_internal_pull(WP_STATUS_PAD);
|
ssus_disable_internal_pull(WP_STATUS_PAD);
|
||||||
|
|
||||||
/* WP is enabled when the pin is reading high. */
|
/* WP is enabled when the pin is reading high. */
|
||||||
|
|
Loading…
Reference in New Issue