docs/design/interrupt-framework-design.rst

275 #. Secure Payload Dispatcher (SPD) service. This service interfaces with the
282    the SPD service. TF-A implements an example Test Secure Payload Dispatcher
283    (TSPD) service.
285    An SPD service plugs into the EL3 runtime firmware and could be common to
290    SPD service to manage communication with non-secure software. TF-A
295    just like the SPD service.
349 particular type of interrupt. A Secure Payload Dispatcher service should use
401 A SPD service is responsible for determining and maintaining the interrupt
408 If the routing model is not known to the SPD service at build time, then it must
415 could either be provided to the SPD service at build time or by the SP at
511    TEL3=1**) where the SPD service will hand them to the SP. This is defined
520 service at compile time, then the SP should pass this information to the SPD
521 service at runtime during its initialisation phase.
537    service during the registration phase. The SPD service would also need to
541    registration phase if it is not known to the SPD service at build time.
550    call the handler registered by the SPD service for Secure-EL1 interrupts.
559    IHF should co-ordinate with the SPD service to transfer execution to the
562    service which indicates that the SP execution has been preempted by a
564    service at compile time then the SP could provide it during the
572    have not effect. The SPD service should register a non-secure interrupt
591 service at build time.
596 interrupts taken in non-secure state and routed through the TSPD service
598 ``tsp_vectors`` to the TSPD service.
689 The SPD service begins handling an interrupt when the EL3 runtime firmware calls
690 the handler function for that type of interrupt. The SPD service is responsible
695    service during registration. It should use the security state of the
701    An SPD service can register a handler for Secure-EL1 and/or Non-secure
721    The SPD service must save the system register context of the current
732    service should be able to handle this preemption or manage secure interrupt
740 secure state if it has been configured to do so. The SPD service and the SP
750 return control back to the SPD service through a SMC32 or SMC64. The SPD service
758 The example TSPD service registers a handler for Secure-EL1 interrupts taken
801 The TSPD service takes the following actions in ``tspd_smc_handler()`` function
879 service takes the following actions in ``tspd_smc_handler()`` function upon
914 receiving control from the SPD service at an entrypoint agreed upon during build
920 an SMC32 or SMC64 to ask the SPD service to do this.
926 service to pass control back to the non-secure state in the last known exception