Julius Werner 683657e93a 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>		2019-12-06 05:23:33 +00:00
..
intel	soc/intel/fsp_broadwell_de: Drop support	2019-11-21 06:43:29 +00:00
memory	drivers/intel/fsp1_0: Drop support	2019-11-21 06:47:43 +00:00
tpm	security/tpm: Drop CAR_GLOBAL_MIGRATION support	2019-11-29 09:08:33 +00:00
vboot	vboot: Clear secdata change flags after factory init	2019-12-06 05:23:33 +00:00
Kconfig	security/intel: Add TXT infrastructure	2019-09-02 04:52:04 +00:00
Makefile.inc	security/intel: Add TXT infrastructure	2019-09-02 04:52:04 +00:00