Lines Matching refs:routing
11 allows EL3 software to configure the interrupt routing behavior. Its main
75 A routing model for a type of interrupt (generated as FIQ or IRQ) is defined as
79 routed to EL3. A routing model is applicable only when execution is not in EL3.
81 The default routing model for an interrupt type is to route it to the FEL in
84 Valid routing models
87 The framework considers certain routing models for each type of interrupt to be
89 following sub-sections describe all the possible routing models and specify
104 secure state. This is a valid routing model as secure software is in
108 state. This is a valid routing model as secure software in EL3 can
112 non-secure state. This is an invalid routing model as a secure interrupt
117 non-secure state. This is a valid routing model as secure software in EL3
126 non-secure software through EL3. This is a valid routing model as secure
131 state. This is a valid routing model as secure software in EL3 can save
138 non-secure state. This is an valid routing model as a non-secure interrupt
142 non-secure state. This is an invalid routing model as there is no valid
150 Secure-EL1/Secure-EL0. This is a valid routing model as secure software
155 Secure-EL1/Secure-EL0. This is a valid routing model as secure software
159 non-secure state. This is an invalid routing model as a secure interrupt
164 non-secure state. This is a valid routing model as secure software in EL3
175 programmed in ``SCR_EL3`` while applying the routing model for a type of
190 same interrupt signal will be forced to the same routing model. This should be
191 borne in mind when choosing the routing model for an interrupt type.
195 signal. So if either one of the interrupt type sets the routing model so
198 effectively routing the other interrupt type also to EL3.
222 of the routing model for a type of interrupt.
240 The ``flags`` field stores the routing model for the interrupt type in
241 bits[1:0]. Bit[0] stores the routing model when execution is in the secure
242 state. Bit[1] stores the routing model when execution is in the non-secure
249 The ``scr_el3[2]`` field also stores the routing model but as a mapping of the
327 interrupt was generated and routed as per the routing model specified
350 interrupts. This API also requires the caller to specify the routing model for
368 Interrupt routing is governed by the configuration of the ``SCR_EL3.FIQ/IRQ`` bits
372 following APIs to let EL3 Runtime Firmware program and retrieve the routing
387 ``set_routing_model()`` API which programs the ``SCR_EL3`` according to the routing
391 runtime firmware is responsible for programming the routing model. The SPD is
392 responsible for ensuring that the routing model has been adhered to upon
399 routing model supported by itself and the Secure Payload. It is also responsible
401 the routing model. It could determine the routing model at build time or at
405 If the routing model is not known to the SPD service at build time, then it must
407 program the routing model only after SP initialisation has completed e.g. in the
419 routing model at build time.
425 - When the build flag ``TSP_NS_INTR_ASYNC_PREEMPT`` is zero, the default routing
433 Secure-EL1. The default routing model is used for non secure interrupts in
488 (Secure-EL1 IHF) to support its chosen interrupt routing model. Secure payload
500 in the routing model where **CSS=1 and TEL3=0**. Secure-EL1 interrupts
501 will be routed to EL3 (as per the routing model where **CSS=1 and
506 both these interrupt handling models depending upon the chosen routing model.
508 The following list briefly describes how the choice of a valid routing model
510 the interrupt routing model is not known to the SPD service at compile time,
569 non-secure state (EL1/EL2) and are not visible to the SP. This routing
580 The routing model for Secure-EL1 and non-secure interrupts chosen by the TSP is
681 generating according to the interrupt routing model specified by the SPD
690 from non-secure state. Also if a routing model is chosen where Secure-EL1
696 routing model and interrupt type. For non secure and S-EL1 interrupt,
726 The routing model allows non-secure interrupts to interrupt Secure-EL1 when in
728 should implement a mechanism for routing these interrupts to the last known
824 the TSPD will set the routing model for the non-secure interrupt to be routed to
828 originated from the secure state and disables routing of non-secure interrupts
836 routing model for non-secure interrupt in secure state is in effect
893 interrupt handling models depending upon the interrupt routing model it has