From ab5a9f937818cbfd1fc686a77c2de818e15d1cfc Mon Sep 17 00:00:00 2001 From: Arthur Heymans Date: Mon, 6 Nov 2023 15:49:24 +0100 Subject: [PATCH] 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 Change-Id: I361731c930a35e12245153920df1b6884d47064c Reviewed-on: https://review.coreboot.org/c/coreboot/+/78938 Tested-by: build bot (Jenkins) Reviewed-by: Martin L Roth --- src/mainboard/google/rambi/chromeos.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/mainboard/google/rambi/chromeos.c b/src/mainboard/google/rambi/chromeos.c index a225821fd8..50497f07aa 100644 --- a/src/mainboard/google/rambi/chromeos.c +++ b/src/mainboard/google/rambi/chromeos.c @@ -31,7 +31,7 @@ int get_write_protect_state(void) * there is a 10K pullup. Disable the internal pull in romstage so that * there isn't any ambiguity in the reading. */ - if (ENV_ROMSTAGE) + if (ENV_ROMSTAGE_OR_BEFORE) ssus_disable_internal_pull(WP_STATUS_PAD); /* WP is enabled when the pin is reading high. */