Lines Matching refs:routing
5 allows EL3 software to configure the interrupt routing behavior. Its main
69 A routing model for a type of interrupt (generated as FIQ or IRQ) is defined as
73 routed to EL3. A routing model is applicable only when execution is not in EL3.
75 The default routing model for an interrupt type is to route it to the FEL in
78 Valid routing models
81 The framework considers certain routing models for each type of interrupt to be
83 following sub-sections describe all the possible routing models and specify
99 secure state. This is a valid routing model as secure software is in
103 state. This is a valid routing model as secure software in EL3 can
107 non-secure state. This is an invalid routing model as a secure interrupt
112 non-secure state. This is a valid routing model as secure software in EL3
121 non-secure software through EL3. This is a valid routing model as secure
126 state. This is a valid routing model as secure software in EL3 can save
133 non-secure state. This is a valid routing model as a non-secure interrupt
137 non-secure state. This is an invalid routing model as there is no valid
147 Secure-EL1/Secure-EL0. This is a valid routing model as secure software
151 However, when ``EL3_EXCEPTION_HANDLING`` is ``1``, this routing model is
157 Secure-EL1/Secure-EL0. This is a valid routing model as secure software
161 non-secure state. This is an invalid routing model as a secure interrupt
166 non-secure state. This is a valid routing model as secure software in EL3
177 programmed in ``SCR_EL3`` while applying the routing model for a type of
192 same interrupt signal will be forced to the same routing model. This should be
193 borne in mind when choosing the routing model for an interrupt type.
197 signal. So if either one of the interrupt type sets the routing model so
200 effectively routing the other interrupt type also to EL3.
221 specification of the routing model for a type of interrupt.
239 The ``flags`` field stores the routing model for the interrupt type in
240 bits[1:0]. Bit[0] stores the routing model when execution is in the secure
241 state. Bit[1] stores the routing model when execution is in the non-secure
248 The ``scr_el3[2]`` field also stores the routing model but as a mapping of the
328 interrupt was generated and routed as per the routing model specified
351 interrupts. This API also requires the caller to specify the routing model for
369 Interrupt routing is governed by the configuration of the ``SCR_EL3.FIQ/IRQ`` bits
373 following APIs to let EL3 Runtime Firmware program and retrieve the routing
388 ``set_routing_model()`` API which programs the ``SCR_EL3`` according to the routing
392 runtime firmware is responsible for programming the routing model. The SPD is
393 responsible for ensuring that the routing model has been adhered to upon
402 routing model supported by itself and the Secure Payload. It is also responsible
404 the routing model. It could determine the routing model at build time or at
408 If the routing model is not known to the SPD service at build time, then it must
410 program the routing model only after SP initialisation has completed e.g. in the
426 routing model at build time.
432 - When the build flag ``TSP_NS_INTR_ASYNC_PREEMPT`` is zero, the default routing
440 Secure-EL1. The default routing model is used for non secure interrupts in
497 (Secure-EL1 IHF) to support its chosen interrupt routing model. Secure payload
509 in the routing model where **CSS=1 and TEL3=0**. Secure-EL1 interrupts
510 will be routed to EL3 (as per the routing model where **CSS=1 and
515 both these interrupt handling models depending upon the chosen routing model.
517 The following list briefly describes how the choice of a valid routing model
518 (see `Valid routing models`_) effects the implementation of the Secure-EL1
519 IHF. If the choice of the interrupt routing model is not known to the SPD
578 non-secure state (EL1/EL2) and are not visible to the SP. This routing
589 The routing model for Secure-EL1 and non-secure interrupts chosen by the TSP is
694 generated according to the interrupt routing model specified by the SPD
703 from non-secure state. Also if a routing model is chosen where Secure-EL1
709 routing model and interrupt type. For non secure and S-EL1 interrupt,
739 The routing model allows non-secure interrupts to interrupt Secure-EL1 when in
741 should implement a mechanism for routing these interrupts to the last known
839 routing model for the non-secure interrupt to be routed to EL3 from secure state
843 routing of non-secure interrupts from secure state to EL3. This is to prevent
850 routing model for non-secure interrupt in secure state is in effect
910 interrupt handling models depending upon the interrupt routing model it has