diff options
| author | Phil Noh <Phil.Noh@amd.com> | 2024-11-13 18:04:15 -0600 |
|---|---|---|
| committer | mergify[bot] <37929162+mergify[bot]@users.noreply.github.com> | 2024-11-26 01:25:03 +0000 |
| commit | c15bd993428ea4f75aae4f885f67903a8f89fae4 (patch) | |
| tree | 1a1a91c710b391c0c382d137761596e93dd0aa62 /Omap35xxPkg | |
| parent | 468b3d9589e5dfb18008fcd27ade67584b95ca83 (diff) | |
| download | edk2-c15bd993428ea4f75aae4f885f67903a8f89fae4.tar.gz edk2-c15bd993428ea4f75aae4f885f67903a8f89fae4.tar.bz2 edk2-c15bd993428ea4f75aae4f885f67903a8f89fae4.zip | |
SecurityPkg/Tcg2Config: Set TPM2.0 for default of Attempt TPM Device
As TPM2.0 is popular, updating default value for the Setup menu supports
a benefit for some systems that have another TPM Setup menu to select
TPM2.0 devices (e.g. dTPM, fTPM) depending on platform bios.
For example, when loading default configuration using F9 key in Setup
(Brower Action: SystemLevel), it is possible for them to load an
unsynchronized value. If user does not adjust the value before saving
Setup, it could influence an unexpected TPM initialization at next boot.
Setting TPM2.0 as default value supports the benefit related to the case.
Signed-off-by: Phil Noh <Phil.Noh@amd.com>
Diffstat (limited to 'Omap35xxPkg')
0 files changed, 0 insertions, 0 deletions