Lines Matching refs:_TPM_Init

163 _TPM_Init..........................................................................................…
1192 The TPM may enter Failure mode during _TPM_Init processing, before TPM2_Startup(). Since
2072 _TPM_Init
2075 _TPM_Init initializes a TPM.
2081 If the TPM performs self-tests after receiving _TPM_Init() and the TPM enters Failure mode before
2085 The means of signaling _TPM_Init shall be defined in the platform-specific specifications that defi…
2113 This function is used to process a _TPM_Init() indication.
2138 void _TPM_Init(void)
2173 TPM2_Startup() is always preceded by _TPM_Init, which is the physical indication that TPM initializ…
2174 is necessary because of a system-wide reset. TPM2_Startup() is only valid after _TPM_Init Additional
2184 …d a platform specific specification may allow these indications between _TPM_Init and TPM2_Startup…
2279 PCR may be initialized any time between _TPM_Init and the end of TPM2_Startup(). PCR that
2999 TPM will remain in Failure mode until the next _TPM_Init.
27401 If lockoutRecovery is zero, then the recovery interval is a boot cycle (_TPM_Init followed by
27828 need to be reset (_TPM_Init and TPM2_Startup(TPM_SU_CLEAR)) before the new PCR settings take
28049 After a _TPM_Init, system software may not be able to resume the field upgrade that was in process
28061 after _TPM_Init matches either of those digests. If so, the firmware update process restarts and the
28085 commands until a _TPM_Init is received.
28090 manner, the TPM is able to indicate the digest of the next block. If a _TPM_Init occurs while the
28092 not, then the TPM will not accept the original firmware until the next _TPM_Init when the TPM is in