Searched refs:scenario (Results 1 – 12 of 12) 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);
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
1180 that continue with original exception. It is the only scenario where EL3 is capable1541 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.
228 The following figure depicts a scenario involving explicit dispatch of SDEI
1378 | | | scheduled call chain. Refer scenario 1 of |1382 | | | different CPU. This scenario is not supported |1399 this secure interrupt. In this scenario, it is SP1.
445 scenario.
487 but they can be modified if needed to better adapt it to a specific scenario.
