On Glymur, enabling QSEECOM exposes EFI boot variables to userspace,
including LoaderTpm2ActivePcrBanks written by systemd-boot. Systemd
reads this variable to detect TPM2 availability and activates
tpm2.target, which waits for /dev/tpm0. Since the TPM firmware (SPSS) is
non-functional on Glymur linux, /dev/tpm0 is never created and systemd
stalls for the full 90-second device timeout, causing kernel CI failures.
Delete LoaderTpm2ActivePcrBanks early in the EFI stub before systemd can
read it, preventing tpm2.target activation.
Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
On Glymur, enabling QSEECOM exposes EFI boot variables to userspace, including LoaderTpm2ActivePcrBanks written by systemd-boot. Systemd reads this variable to detect TPM2 availability and activates tpm2.target, which waits for /dev/tpm0. Since the TPM firmware (SPSS) is non-functional on Glymur linux, /dev/tpm0 is never created and systemd stalls for the full 90-second device timeout, causing kernel CI failures.
The boot team identified that no other SoC will have this variable set and we can safely delete it. So delete LoaderTpm2ActivePcrBanks early in the EFI stub before systemd can read it, preventing tpm2.target activation.