Searched refs:scenario (Results 1 – 17 of 17) sorted by relevance
309 void spm_output_wake_reason(struct wake_status *wakesta, const char *scenario) in spm_output_wake_reason() argument315 scenario, wakesta->assert_pc, mmio_read_32(ULPOSC_CON)); in spm_output_wake_reason()322 scenario, wakeup_src_str[i], wakesta->timer_out); in spm_output_wake_reason()
2545 const char *scenario);
35 disclosure depending on the deployment scenario and hypervisor configuration.
55 To help in the latter scenario, the ``SPIN_ON_BL1_EXIT=1`` build option can be
161 scenario:
535 synchronous interrupt handling model. The SP could implement this scenario666 registered for this type of interrupt. This scenario is reported as an
1225 that continue with original exception. It is the only scenario where EL3 is capable1601 unlikely scenario where a CVE and an erratum numbers clash, the CVE number
79 entered in a cold boot scenario.
473 In the scenario when secure interrupt occurs while the secure partition is running,479 The 'managed exit' scenario is the responsibility of the TOS and the SPMC is not involved.
351 The figure above illustrates a scenario on FVP for one of the build453 lower exception levels of Secure and Realm worlds. In this scenario, we save the
228 The following figure depicts a scenario involving explicit dispatch of SDEI
100 eliminating the need for panic handling in this scenario.
418 scenario.
487 but they can be modified if needed to better adapt it to a specific scenario.
384 handle this scenario.
784 safely in scenario where NS-EL2 is present but unused. This flag is set to 0
2205 …- handle invalid entry point in cpu hotplug scenario ([435bc14](https://review.trustedfirmware.org…2216 …- handle invalid entry point in cpu hotplug scenario ([e5e417d](https://review.trustedfirmware.org…2229 …- handle invalid entry point in cpu hotplug scenario ([df44616](https://review.trustedfirmware.org…