• Home
  • Raw
  • Download

Lines Matching refs:EL3

5 Firmware (BL31) that are targeted at EL3, other than SMCs. The |EHF| takes care
6 of the following exceptions when targeted at EL3:
24 allows for asynchronous exceptions to be routed to EL3. As described in the
29 FIQs and IRQs routed to EL3 are not required to be handled in EL3.
32 exceptions are targeted at and handled in EL3. For instance:
47 first received by the EL3 firmware, and then dispatched to Normal world
51 suitably routed to EL3, and the Runtime Firmware (BL31) is extended to include
53 EL3. These components—referred to as *dispatchers* [#spd]_ in general—may
58 - Receive and handle exceptions entirely in EL3, meaning the exceptions
59 handling terminates in EL3.
61 - Receive exceptions, but handle part of the exception in EL3, and delegate the
65 - Receive exceptions, but handle part of the exception in EL3, and delegate
77 <firmware_design_sel1_spd>`, which is an EL3 component that operates in EL3
86 for, and handle exceptions targeted at EL3. This section outlines the basics,
108 executing in EL3, or has delegated the execution to a lower EL. For interrupts,
109 this is implicit when an interrupt is targeted and acknowledged at EL3, and the
143 top-level handler for interrupts that target EL3, as described in the
149 EL3. As a result, S-EL1 software cannot expect to handle Non-secure
151 as :ref:`CSS=0, TEL3=0 <EL3 interrupts>`.
155 are received at EL3, but are then :ref:`synchronously <sp-synchronous-int>`
159 set to ``1`` so that *Group 0* interrupts target EL3.
279 The parameters are as obtained from the top-level :ref:`EL3 interrupt handler
331 /* List interrupt properties for GIC driver. All interrupts target EL3 */
455 execution. As discussed elsewhere in this document, EL3 execution, and any
536 with the :ref:`Interrupt Management Framework<el3-runtime-firmware>` for EL3
539 #. When an interrupt belonging to a dispatcher fires, GIC raises an EL3/Group 0
540 interrupt, and is taken to EL3.
542 #. The top-level EL3 interrupt handler executes. The handler acknowledges the
558 The following is an example flow for exceptions that targets EL3 other than
568 handler may choose to do the handling entirely in EL3 or delegate to a lower