Lines Matching refs:handled
48 1. It should be possible to route interrupts meant to be handled by secure
57 2. It should be possible to route interrupts meant to be handled by
69 1. All secure interrupts are handled in Secure-EL1. They can be delivered to
70 Secure-EL1 via EL3 but they cannot be handled in EL3. It will be possible
80 the exception level(s) it is handled in.
84 context. It is always handled in Secure-EL1.
88 current execution context. It is always handled in either Non-secure EL1
93 always handled in EL3.
177 is handled by non-secure software.
439 non-secure state. Any non-secure interrupts will be handled as described
463 If `PSTATE.F=1` then Secure-EL1 interrupts will be handled as per the
473 non-secure state. They should be handled through the synchronous interrupt
488 non-secure state where the interrupt should be handled e.g the SP could
502 the non-secure state where the interrupt will be handled. The Secure-EL1
505 3. __CSS=1, TEL3=0__. Non-secure interrupts are handled in the FEL in
549 lower exception level using AArch64 or AArch32 are handled.
671 the interrupt has been successfully validated and ready to be handled at a
679 handled.
717 now be handled by the SP. `x1` is written with the value of `elr_el3`
810 level. This will allow the non-secure interrupt to be handled in the non-secure
835 1. Secure-EL1 interrupts are handled by calling the `tsp_fiq_handler()`
838 2. Non-secure interrupts are handled by issuing an SMC64 with `TSP_PREEMPTED`