Lines Matching full:routing
10 - [Routing Model](#122-routing-model)
11 - [Valid Routing Models](#123-valid-routing-models)
45 allows EL3 software to configure the interrupt routing behavior. Its main
106 #### 1.2.2 Routing model
116 A routing model for a type of interrupt (generated as FIQ or IRQ) is defined as
120 routed to EL3. A routing model is applicable only when execution is not in EL3.
122 The default routing model for an interrupt type is to route it to the FEL in
125 #### 1.2.3 Valid routing models
126 The framework considers certain routing models for each type of interrupt to be
128 following sub-sections describe all the possible routing models and specify
142 secure state. This is a valid routing model as secure software is in
146 state. This is a valid routing model as secure software in EL3 can
150 non-secure state. This is an invalid routing model as a secure interrupt
155 non-secure state. This is a valid routing model as secure software in EL3
164 non-secure software through EL3. This is a valid routing model as secure
169 state. This is a valid routing model as secure software in EL3 can save
176 non-secure state. This is an valid routing model as a non-secure interrupt
180 non-secure state. This is an invalid routing model as there is no valid
191 programmed in `SCR_EL3` while applying the routing model for a type of
206 of the routing model for a type of interrupt.
224 The `flags` field stores the routing model for the interrupt type in
225 bits[1:0]. Bit[0] stores the routing model when execution is in the secure
226 state. Bit[1] stores the routing model when execution is in the non-secure
233 The `scr_el3[2]` field also stores the routing model but as a mapping of the
308 interrupt was generated and routed as per the routing model specified
325 interrupts. This API also requires the caller to specify the routing
343 Interrupt routing is governed by the configuration of the `SCR_EL3.FIQ/IRQ` bits
347 following APIs to let EL3 Runtime Firmware program and retrieve the routing
360 `set_routing_model()` API which programs the `SCR_EL3` according to the routing
364 runtime firmware is responsible for programming the routing model. The SPD is
365 responsible for ensuring that the routing model has been adhered to upon
370 routing model supported by itself and the Secure Payload. It is also responsible
372 the routing model. It could determine the routing model at build time or at
376 If the routing model is not known to the SPD service at build time, then it must
378 program the routing model only after SP initialisation has completed e.g. in the
388 routing model at build time.
394 * The default routing model is used for non-secure interrupts i.e they are
428 (Secure-EL1 IHF) to support its chosen interrupt routing model. Secure payload
440 in the routing model where __CSS=1 and TEL3=0__. Secure-EL1 interrupts
441 will be routed to EL3 (as per the routing model where __CSS=1 and
446 both these interrupt handling models depending upon the chosen routing model.
448 The following list briefly describes how the choice of a valid routing model
450 the interrupt routing model is not known to the SPD service at compile time,
506 non-secure state (EL1/EL2) and are not visible to the SP. This routing
516 The routing model for Secure-EL1 and non-secure interrupts chosen by the TSP is
609 generating according to the interrupt routing model specified by the SPD
632 to the secure interrupt handler. If the routing model chosen is such
644 where the interrupt was generated. This depends upon the routing model and
674 The routing model allows non-secure interrupts to be taken to Secure-EL1 when in
676 routing these interrupts to the last known exception level in the non-secure
793 interrupt handling models depending upon the interrupt routing model it has
