Lines Matching full:cold
14 world in DRAM. This is the cold boot path.
35 Cold boot
38 The cold boot path starts when the platform is physically turned on. If
41 CPU is chosen through platform-specific means. The cold boot path is mainly
49 The cold boot path in this implementation of the ARM Trusted Firmware,
80 - initialization and execution of the first three stages during cold boot
102 boot and a cold boot. This is done using platform-specific mechanisms (see the
105 entrypoint. In the case of a cold boot, the secondary CPUs are placed in a safe
107 the `Porting Guide`_) while the primary CPU executes the remaining cold boot path
505 world cold boot, ensuring that no secure state information finds its way into
522 Required CPU state when calling ``bl31_entrypoint()`` during cold boot
568 Cold boot Initialization parameters. This data may need to be cleaned out of
583 Data structures used in the BL31 cold boot interface
643 Required CPU state when entering during cold boot
679 via the Cold boot Initialization parameters. This data may need to be cleaned
694 Data structures used in cold boot interface
697 The AArch32 EL3 Runtime Software cold boot interface uses ``bl_params`` instead
699 described in AArch64 BL31 cold boot interface section.
812 framework running on the primary CPU during cold boot as part of the BL31
834 function is only invoked on the primary CPU during cold boot. If the service
1154 perform actions very early after a CPU is released from reset in both the cold
1331 both cold and warm boots, shortly after reset. Individual Errata workarounds are
1651 cold boot.
2031 ``level`` and ``lock_index`` are only written once during cold boot. Hence removing
