summaryrefslogtreecommitdiff
path: root/src/ec/google
diff options
context:
space:
mode:
authorJulius Werner <jwerner@chromium.org>2019-12-04 12:50:43 -0800
committerJulius Werner <jwerner@chromium.org>2019-12-06 05:23:33 +0000
commit683657e93ac52a194807d824d417e7fc3226ee9d (patch)
tree09b62d56fdeefb5a4e04aac7903e0d16fb3fe123 /src/ec/google
parent1debc0c1019159396ca2f72874938a991bb3246e (diff)
downloadcoreboot-683657e93ac52a194807d824d417e7fc3226ee9d.tar.xz
vboot: Clear secdata change flags after factory init
factory_initialize_tpm() calls secdata_xxx_create() (for both firmware and kernel space) and then immediately writes those spaces out to the TPM. The create() functions make vboot think it just changed the secdata (because it reinitialized the byte arrays in the context), so we also need to clear the VB2_CONTEXT_SECDATA_xxx_CHANGED flags again, otherwise vboot thinks it still needs to flush the spaces out to the TPM even though we already did that. Also clean up some minor related stuff (VB2_CONTEXT_SECDATA_CHANGED notation is deprecated, and secdata space intialization should use the same write-and-readback function we use for updates). Change-Id: I231fadcf7b35a1aec3b39254e7e41c3d456d4911 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/37471 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Aaron Durbin <adurbin@chromium.org>
Diffstat (limited to 'src/ec/google')
0 files changed, 0 insertions, 0 deletions