Tom Rini 021baf7b08 We have use cases where a previous stage boot loader doesn't have any
TPM drivers. Instead of extending the hardware PCRs it produces an
 EventLog that U-Boot later replays on the hardware.
 
 The only real example we have is TF-A, which produces the EventLog using
 hashing algorithms created at compile time. This creates a problem to the
 TPM since measurements need to extend all active PCR banks. Up to now
 we were exiting refusing the extend measurements.
 
 TPMs can be instructed to change their active PCR banks, as long as the
 device resets immediately after a reconfiguration. This PR is adding
 that functionality. U-Boot can now scan the currently active TPM PCR
 banks, the ones it was compiled to support and the ones present in an
 EventLog. It the reconfigures the TPM on the fly with the correct algorithms.
 -----BEGIN PGP SIGNATURE-----
 
 iQIzBAABCgAdFiEEgWII69YpahbL5iK5gS8AYozs+qIFAmeYhMUACgkQgS8AYozs
 +qIzfxAAv0vngk2MycOWsQY1Mch0799o+QPN+J4avl52duLSCmiFUpoXOQCiRZSG
 5SpjqygrWXOL6T0EUMVjv8qaGJTZY5uY296G8zt+Nboq08XRMb76kV3vl/9XQ9oh
 lsF44QcoSpWM+NCfQ00yWsmy1FQZg5soQMU1liW8qJH1yUuDZP7WGDG2N2Kng5ag
 MW38SWXVM8+RiA1UeuaQtVvH5BfL/kotsG4U2LZwp6k4eJttzbUQylF09K/h+4Qf
 8nIwl6TQ7j59DRA2r7WHVmxFpYf+BOzf7wnLbAKKP9/QlEEo8+K8GabrNqcm/dx+
 Bav6dzZUzAJ024ocvouanQmjJfj2WnqryfRNJrU3ggt2j6JXkjNW9xHXdBZoKRBj
 WNTXMUIxe1t+5jD9KXyAg/C7FE1EaJDZu0JfK0xeXHvnnYbL6eYHyRkZCA6MZ95O
 ZCvDXv9x7zhZkUj9VY5kFvmWbemjX33CHMToIafu7fZtsCe6oIrISzMW4T3/74pS
 y6142Ceoy7qxYCkBgTzt5UTj4pTS2ZYaiqZXUTftFtmaNt56lcFWqaTR7Fz1U8CV
 1K8I3wKs8Fs5P326Y9fJ/kHfhHFTaVVDxWIhxK5Mg+vAIPeNECDybYH4q0FzAf1K
 h9ni39KC629MpMB2drYmYCtrzGk4nSyAwha1vSS9twltFi4Rgmo=
 =jn1D
 -----END PGP SIGNATURE-----

Merge tag 'tpm-master-28012025' of https://source.denx.de/u-boot/custodians/u-boot-tpm

CI: https://source.denx.de/u-boot/custodians/u-boot-tpm/-/pipelines/24375

We have use cases where a previous stage boot loader doesn't have any
TPM drivers. Instead of extending the hardware PCRs it produces an
EventLog that U-Boot later replays on the hardware.

The only real example we have is TF-A, which produces the EventLog using
hashing algorithms created at compile time. This creates a problem to the
TPM since measurements need to extend all active PCR banks. Up to now
we were exiting refusing the extend measurements.

TPMs can be instructed to change their active PCR banks, as long as the
device resets immediately after a reconfiguration. This PR is adding
that functionality. U-Boot can now scan the currently active TPM PCR
banks, the ones it was compiled to support and the ones present in an
EventLog. It the reconfigures the TPM on the fly with the correct algorithms.
2025-01-29 08:12:21 -06:00
..
2024-12-09 16:29:47 -06:00
2022-10-30 20:07:16 +01:00
2022-01-19 18:11:34 +01:00
2022-09-29 16:07:57 -04:00
2024-10-17 03:12:47 +02:00
2022-09-24 10:47:01 -04:00
2025-01-22 15:58:03 -06:00
2022-07-26 02:30:56 -06:00
2023-08-08 10:22:03 -04:00
2024-07-29 15:01:04 -06:00
2023-12-21 08:54:37 -05:00
2022-01-30 01:25:00 +00:00
2022-01-30 01:25:00 +00:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2024-10-24 11:20:58 -06:00
2024-07-29 15:01:04 -06:00
2024-08-26 14:05:38 -06:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2024-02-13 15:38:49 -05:00
2024-07-29 15:01:04 -06:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2024-11-20 17:57:58 +01:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2024-07-29 15:01:04 -06:00
2022-01-19 18:11:34 +01:00
2025-01-05 02:30:49 +01:00
2024-06-14 12:59:07 -06:00
2024-08-26 14:05:38 -06:00
2022-03-15 16:19:29 -04:00
2022-04-06 14:01:42 -04:00
2024-07-29 15:01:04 -06:00
2023-05-02 14:23:34 -04:00
2022-01-19 18:11:34 +01:00
2024-09-24 13:41:20 -06:00
2022-10-18 09:32:53 +08:00
2023-01-20 12:27:06 -05:00
2024-07-29 15:01:04 -06:00
2024-07-29 15:01:04 -06:00
2022-07-26 11:29:00 +02:00
2024-07-29 15:01:04 -06:00
2023-11-07 14:50:51 -05:00
2024-07-29 15:01:04 -06:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2024-08-13 06:23:15 +02:00
2022-01-19 18:11:34 +01:00
2023-04-27 13:51:06 -04:00
2022-01-19 18:11:34 +01:00
2023-12-21 11:59:49 -05:00
2024-10-10 16:02:20 -06:00
2022-10-30 20:07:17 +01:00
2024-12-31 10:58:30 -06:00
2025-01-26 11:06:56 +01:00
2024-07-29 15:01:04 -06:00
2023-12-21 08:54:37 -05:00
2024-11-04 16:41:38 -06:00
2024-07-29 15:01:04 -06:00
2022-01-24 10:35:10 -05:00
2024-07-29 15:01:04 -06:00
2024-10-24 11:21:48 -06:00
2024-07-29 15:01:04 -06:00
2024-07-29 15:01:04 -06:00
2023-12-21 08:54:37 -05:00
2024-11-25 23:07:37 -03:00
2024-09-30 17:48:12 -06:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2024-11-20 17:57:58 +01:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2023-01-16 18:01:10 +08:00
2024-09-12 17:35:37 +02:00
2023-12-21 08:54:37 -05:00
2024-07-29 15:01:04 -06:00
2022-04-01 15:03:13 -04:00
2025-01-14 14:29:29 -06:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2024-07-29 15:01:04 -06:00
2025-01-22 09:47:50 -06:00
2022-04-06 14:03:17 -04:00
2023-10-09 15:24:31 -04:00
2023-02-10 07:41:40 -05:00
2024-07-29 15:01:04 -06:00
2022-01-19 18:11:34 +01:00
2025-01-07 15:45:51 +02:00
2022-01-19 18:11:34 +01:00
2025-01-01 10:40:33 -06:00
2022-01-19 18:11:34 +01:00
2024-07-29 15:01:04 -06:00
2022-12-07 16:04:17 -05:00
2024-07-29 15:01:04 -06:00
2022-01-19 18:11:34 +01:00
2022-01-19 18:11:34 +01:00
2024-11-13 08:14:23 -06:00
2022-01-19 18:11:34 +01:00
2024-07-29 15:01:04 -06:00