It seems to me that the firmware of the laptop doesn't count on "Setup" to record the system settings but adds the information gradually during the boot process. Thus, the content of "Setup" contains lots of additional information in Runtime.
I wonder if we should calculate PCR 1 and 3 only based on the data recorded in the TPM event log.
I think PCR 1 is mostly useless when it comes to sealing storage against. PCR 1 is described as holding "BIOS configuration", and I would tend to ignore that. So yes, I agree with you.
There is another PCR mismatch in the laptop, and here is the event that causes it:
Setup-ec87d643-eba4-4bb5-a1e5-3f3e36b20da9 is not in the "Globally Defined Variables" in UEFI SPEC, and the implementation varies among different platforms. For example, in the Minnowboard firmware, it's "NV+BS": https://github.com/tianocore/edk2-platforms/blob/master/Platform/Intel/Vlv2TbltDevicePkg/PlatformSetupDefaults.dsc#L10 But in WhitleyOpenBoard, it's "NV+BS+RT": https://github.com/tianocore/edk2-platforms/blob/master/Platform/Intel/WhitleyOpenBoardPkg/StructurePcd.dsc#L24 In general, it's a variable to reflect the system setings.
It seems to me that the firmware of the laptop doesn't count on "Setup" to record the system settings but adds the information gradually during the boot process. Thus, the content of "Setup" contains lots of additional information in Runtime.
I wonder if we should calculate PCR 1 and 3 only based on the data recorded in the TPM event log.