Lines Matching refs:handler

220    #. Providing an interface to allow registration of a handler and
224       registered handler when the interrupt is generated.
234             interrupt_type_handler_t handler;
301 `Software components`_) during the registration of a handler for an interrupt
309 This component declares the following prototype for a handler of an interrupt type.
327    in the secure state. This bit can be used by the handler to ensure that
336 Once the handler routine completes, execution will return to either the secure
337 or non-secure state. The handler routine must return a pointer to
340 appropriate ``cpu_context`` to be used is expected to be set by the handler
342 A portable interrupt handler implementation must set the target context both in
344 library APIs. The handler should treat all error conditions as critical errors
348 The runtime firmware provides the following API for registering a handler for a
350 this API to register a handler for Secure-EL1 and optionally for non-secure
357                                             interrupt_type_handler handler,
365 ``-EALREADY`` in case a handler for the interrupt type has already been
366 registered. If the ``type`` is unrecognised or the ``flags`` or the ``handler`` are
405 runtime. It must use this information to register a handler for each interrupt
448    ``tsp_vectors`` in the SP which also includes the handler for Secure-EL1
458 #. The TSPD implements a handler function for Secure-EL1 interrupts. This
475    implements a handler function for non-secure interrupts. This function is
550    call the handler registered by the SPD service for Secure-EL1 interrupts.
573    handler which should save the SP state correctly and resume execution in
656 #. Determining the handler for the type of interrupt that has been generated.
663    It returns the reference to the registered handler for this interrupt
664    type. The ``handler`` is retrieved from the ``intr_type_desc_t`` structure as
665    described in Section 2. ``NULL`` is returned if no handler has been
669 #. Calling the registered handler function for the interrupt type generated.
672    structure for the current security state are passed to the handler function
675    The handler function returns a reference to the per-cpu ``cpu_context_t``
679    the security state determined by the handler routine. The ``el3_exit()``
690 the handler function for that type of interrupt. The SPD service is responsible
696    exception level (passed in the ``flags`` parameter of the handler) where
698    recognised then the handler should treat it as an irrecoverable error
701    An SPD service can register a handler for Secure-EL1 and/or Non-secure
705    S-EL1 interrupt should never be routed to EL3 from secure state. The handler
735 #. Setting the return value of the handler to the per-cpu ``cpu_context`` if
758 The example TSPD service registers a handler for Secure-EL1 interrupts taken
760 Secure-EL1 interrupts are handled in S-EL1 by TSP. Its handler
841 non-secure interrupt handler. The ``tspd_ns_interrupt_handler()`` on being
855 identifier to signal preemption of TSP. The TSPD SMC handler,
996     /* The pending non-secure interrupt is handled by the interrupt handler
1004 interrupt causes an IRQ exception and the IRQ handler registered at the