vboot: do not set VBSD_BOOT_FIRMWARE_WP_ENABLED flag
The value of "write protect" GPIO shall be read in depthcharge, and the flag shall be set there instead. BUG=b:124141368, b:124192753, chromium:1556855 TEST=Build locally CQ-DEPEND=CL:1556855 BRANCH=none Change-Id: I4d24a057b1385244a836a67c565ee6726a894fdc Signed-off-by: Joel Kitching <kitching@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/32234 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Furquan Shaikh <furquan@google.com> Reviewed-by: Julius Werner <jwerner@chromium.org>
This commit is contained in:
parent
ae0fb762a2
commit
a751445de4
|
@ -58,9 +58,6 @@ static void fill_vboot_handoff(struct vboot_handoff *vboot_handoff,
|
|||
vb_sd->data_used = sizeof(VbSharedDataHeader);
|
||||
vb_sd->fw_version_tpm = vb2_sd->fw_version_secdata;
|
||||
|
||||
if (get_write_protect_state())
|
||||
vb_sd->flags |= VBSD_BOOT_FIRMWARE_WP_ENABLED;
|
||||
|
||||
if (vb2_sd->recovery_reason) {
|
||||
vb_sd->firmware_index = 0xFF;
|
||||
if (vb2_sd->flags & VB2_SD_FLAG_MANUAL_RECOVERY)
|
||||
|
|
Loading…
Reference in New Issue