Lines Matching refs:interrupt

26 at EL2 and an event dispatch resulting from the triggering of a bound interrupt.
31 As part of initialisation, the SDEI client binds a Non-secure interrupt [1], and
37 At a later point in time, when the bound interrupt triggers [9], it's trapped to
38 EL3. The interrupt is handed over to the SDEI dispatcher, which then arranges to
41 original EL2 execution [13]. Note that the SDEI interrupt remains active until
66 -  For an event that has a backing interrupt, the interrupt number the event is
79 result of receiving an SDEI interrupt), the macro ``SDEI_EXPLICIT_EVENT()``
130    bound to (or released from) any Non-secure interrupt at runtime via the
133 -  ``SDEI_MAPF_BOUND``: Marks the event as statically bound to an interrupt.
216 activity, such as receiving a Secure interrupt or an exception.
235 unlike in `general SDEI dispatch`_, this doesn't involve interrupt binding, as
372 A bound event is an SDEI event that corresponds to a client interrupt.
374 an SDEI event with a client interrupt. There is a possibility that a rogue
375 client can request an invalid interrupt to be bound. This may potentially
378 Even though TF-A implementation has checks to ensure that interrupt ID passed
387 mechanism in place to remove such interrupt source from the system.
409                      External Abort*, *Fault Handling interrupt* or *Error
410                      Recovery interrupt* from one of RAS nodes in the system.