Lines Matching refs:orderly

2520 // Read orderly shutdown states from previous power cycle
2669 // Initialize the orderly shut down flag for this cycle to SHUTDOWN_NONE.
2698 For a shutdownType of any type, the volatile portion of Clock is saved to NV memory and the orderly
2915 // Save all orderly data
2930 // Write orderly shut down state
3628 …utdown() is not required after this comm and in order to reestablish the orderly state of the TPM.…
3630 session is context saved, the orderly state does change.
12645 // been an orderly shutdown. If so, and the selected PCR is one of the
12646 // state saved PCR, then the orderly state has to change. The orderly state
12648 // NOTE: This doesn't just check for Shutdown(STATE) because the orderly
12651 // check to see if there was an orderly shutdown and not do anything if
13126 // orderly state should be cleared because of the reporting of clock info
13477 // orderly state should be cleared because of the reporting of clock info
13794 // orderly state should be cleared because of the reporting of clock info
14143 // orderly state should be cleared because of the reporting of clock info
14474 // orderly state should be cleared because of the update in
14792 // orderly state should be cleared because of the reporting of clock info
25707 // Only need to update NV if changing the orderly state
25723 // orderly state should be cleared because of the update to state clear data
25961 // need to update orderly state
26193 // orderly state should be cleared because of the update to state clear data
26411 // orderly state should be cleared because of the update to state clear data
26746 // Update the DRBG state whenever writing orderly state to NV
26754 // orderly state should be cleared because of the update to state clear data
27167 // orderly state should be cleared
29142 // orderly state should be cleared because of the update of state reset and
29600 // orderly state should be cleared because of the update of state
31721 goes through an orderly shutdown process. The TPM may update the counter value in RAM and
31722 occasionally update the non-volatile version of the counter. An orderly shutdown is one occasion to
31726 reported value. If the TPMA_NV_ORDERLY attribute is not SET, or if the TPM experienced an orderly
31728 TPM shutdown was not orderly, then the TPM shall OR MAX_ORDERLY_COUNT to the contents of the
31747 (orderly or not) of the TPM.
33232 TPM_NV_COUNTER both SET, then in the Event of a non-orderly shutdown, the non-volatile value
33435 // If this is an orderly counter that just rolled over, need to be able to
33734 // If the Index is not-orderly, or if this is the first write, NV will
34034 // If the Index is not-orderly, or if this is the first write, NV will
35640 // orderly state should be cleared because of the reporting of clock info