To match the Linux driver being added upstream we will need to support the old UUID again (see https://patchwork.kernel.org/patch/11033277/ and related). Rolling back the UUID here will require updates to the UEFI and Windows drivers to match.
Any data stored in the TPM under the old UUID will become inaccessible with the new UUID.
If a very old version of the TPM was used there may be a storage conflict. This can be fixed by compiling OP-TEE with CFG_RPMB_RESET_FAT=y. This will wipe ALL persistent objects stored by OP-TEE in RPMB.
To match the Linux driver being added upstream we will need to support the old UUID again (see https://patchwork.kernel.org/patch/11033277/ and related). Rolling back the UUID here will require updates to the UEFI and Windows drivers to match.
Any data stored in the TPM under the old UUID will become inaccessible with the new UUID.
If a very old version of the TPM was used there may be a storage conflict. This can be fixed by compiling OP-TEE with
CFG_RPMB_RESET_FAT=y. This will wipe ALL persistent objects stored by OP-TEE in RPMB.