Lines Matching refs:handling

14    respect to their delivery and handling without the possibility of
64 to the First Exception Level (FEL) capable of handling interrupts. When
100    control of handling secure interrupts.
104    handover the interrupt to Secure-EL1 for handling.
113    can handover the interrupt to Secure-EL1 for handling.
139    non-secure software for handling.
149    by EL3 interrupt and can handover the interrupt to EL3 for handling.
154    handling<interrupt-handling>` documentation.
218    managed by the interrupt handling framework. This entails:
259 handling of interrupts.
496 A Secure Payload must implement an interrupt handling framework at Secure-EL1
503    handling interrupts. This mode applies to both Secure-EL1 and non-secure
512    as the **synchronous mode** of handling interrupts.
514 The interrupt handling framework implemented by the SP should support one or
515 both these interrupt handling models depending upon the chosen routing model.
532    IHF should implement support for handling FIQ interrupts asynchronously.
535    synchronous interrupt handling model. The SP could implement this scenario
545    handling model as described in 1. above.
552    synchronous interrupt handling model described in 1. above.
595 The TSP implements an entrypoint (``tsp_sel1_intr_entry()``) for handling Secure-EL1
597 (synchronous handling model). It passes the reference to this entrypoint via
601 ``early_exceptions`` variable, with a vector table capable of handling FIQ and IRQ
604 VBAR_EL1. It caters for the asynchronous handling model.
611 Interrupt handling
615 Section `Software components`_) in handling an interrupt of a particular type.
689 The SPD service begins handling an interrupt when the EL3 runtime firmware calls
711    generated is not the same as the security state required for handling
728    per the synchronous interrupt handling model it implements. A Secure-EL1
730    that SP execution can be preempted while handling an interrupt by a
749 When the Secure Payload has finished handling a Secure-EL1 interrupt, it could
755 Test secure payload dispatcher Secure-EL1 interrupt handling
792 The figure below describes how the interrupt handling is implemented by the TSPD
799 signal completion of interrupt handling.
820 Test secure payload dispatcher non-secure interrupt handling
831 the TSP either for Secure-EL1 interrupt handling or for resuming the preempted
845 handling Secure-EL1 interrupts that triggered while execution was in the normal
847 ``tspd_handle_sp_preemption()`` for further handling.
859 further handling.
906 Secure payload interrupt handling
910 interrupt handling models depending upon the interrupt routing model it has
913 In the synchronous model, it should begin handling a Secure-EL1 interrupt after
915 time or during the registration phase. Before handling the interrupt, the SP
917 normal execution in the SP later e.g. ``SPSR_EL1``, ``ELR_EL1``. After handling
922 In the asynchronous model, the Secure Payload is responsible for handling
967    dispatcher non-secure interrupt handling`_).
976 interrupt and the execution can return to the non-secure world for handling
1020 .. |Image 1| image:: ../resources/diagrams/sec-int-handling.png
1021 .. |Image 2| image:: ../resources/diagrams/non-sec-int-handling.png