• Home
  • Raw
  • Download

Lines Matching refs:orderly

1561 …next three sections define the structures for the NV data areas: persistent, orderly, and state sa…
2115 324 // ORDERLY_DATA data structure written on each orderly shutdown
2246 …This flag indicates if the execution of a command should cause the orderly state to be cleared. Th…
2249 …g_updateNV. If this flag is TRUE, and the orderly state is not SHUTDOWN_NONE, then the orderly sta…
2413 456 // The orderly state for current cycle
2475 506 // orderly way, then the sClock value is used to initialize the clock. If the
2476 507 // TPM shutdown was not orderly, then the persistent value is used and the safe
2479 510 UINT64 clock; // The orderly version of clock
8652 39 // If DA has not been disabled and the previous shutdown is not orderly
9996 c) set the lower bits in orderly counters to 1 for a non-orderly startup
10046 679 // Reset NV data for orderly values that are not counters
10069 697 // Set the lower bits in an orderly counter to 1 for a non-orderly startup
10094 722 // No write to NV because an orderly shutdown will update the
10576 1049 // Check to see if process for an orderly index is required.
10586 1059 // NV update does not happen for orderly index. Have
10588 1061 // NV and an orderly shutdown is required. Only going to do this if we
10593 1066 // Need to process this part if the Index isn't orderly or if it is
10594 1067 // an orderly counter that just rolled over.
15209 10 // Read orderly data info from NV memory
15212 13 // Read orderly shut down state flag
15215 16 // If the previous cycle is orderly shut down, the value of the safe bit
15341 111 // Get the DRBG state before updating orderly data
18707 310 flags.orderly = SET;
21820 1660 // If the shutdown was orderly, then the values recovered from NV will
21821 1661 // be OK to use. If the shutdown was not orderly, then a TPM Reset was required
25338 memory for the state to be stored on an orderly shutdown. The GET_PUT enum is used by