Lines Matching refs:orderly

1599 32       // Read orderly shutdown states from previous power cycle
1602 35       // See if the orderly state indicates that state was saved
1717 140       // Initialize the orderly shut down flag for this cycle to SHUTDOWN_NONE.
1747 For a shutdownType of any type, the volatile portion of Clock is saved to NV memory and the orderly
1847 31       // Save all orderly data
1865 49       // Write orderly shut down state
2340 …establish the orderly state of the TPM. This is because the created cont ext will occupy an availa…
2342                  session is context saved, the orderly state does change.
7169 31           // been an orderly shutdown. If so, and the selected PCR is one of the
7170 32           // state saved PCR, then the orderly state has to change. The orderly state
7172 34           // NOTE: This doesn't just check for Shutdown(STATE) because the orderly
7175 37           // check to see if there was an orderly shutdown and not do anything if
7456 58       // orderly state should be cleared because of the reporting of clock info
7636 66       // orderly state should be cleared because of the reporting of clock info
7801 69       // orderly state should be cleared because of the reporting of clock info
7985 67       // orderly state should be cleared because of the reporting of clock info
8162 65           // orderly state should be cleared because of the update in
8331 56       // orderly state should be cleared because of the reporting of clock info
14218  86           // Only need to update NV if changing the orderly state
14235 103           // orderly state should be cleared because of the update to state clear data
14369 46               // need to update orderly state
14514 51       // orderly state should be cleared because of the update to state clear data
14636 53       // orderly state should be cleared because of the update to state clear data
14809 79       // Update the DRBG state whenever writing orderly state to NV
14819 89       // orderly state should be cleared because of the update to state clear data
15048 39           // orderly state should be cleared
16139 176       // orderly state should be cleared because of the update of state reset and
16371 133          // orderly state should be cleared because of the update of state
17564 goes through an orderly shutdown process. The TPM may update the counter value in RAM and
17565 occasionally update the non-volatile version of the counter. An orderly shutdown is one occasion to
17570 reported value. If the TPMA_NV_ORDERLY attribute is not SET, or if the TPM experienced an orderly
17572 TPM shutdown was not orderly, then the TPM shall OR MAX_ORDERLY_COUNT to the contents of the
17586                 (orderly or not) of the TPM.
18362 …       TPM_NV_COUNTER both SET, then in the Event of a non-orderly shutdown, the non-volatile value
18461 41       // If this is an orderly counter that just rolled over, need to be able to
18613 32       // If the Index is not-orderly, or if this is the first write, NV will
18780 41       // If the Index is not-orderly and it has changed, or if this is the first
19621  95      // orderly state should be cleared because of the reporting of clock info