Lines Matching refs:SPD

275 #. Secure Payload Dispatcher (SPD) service. This service interfaces with the
282    the SPD service. TF-A implements an example Test Secure Payload Dispatcher
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.
392 runtime firmware is responsible for programming the routing model. The SPD is
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
409 be provided by the SP as the result of its initialisation. The SPD should
411 SPD initialisation function pointed to by the ``bl32_init`` variable.
413 The SPD should determine the mechanism to pass control to the Secure Payload
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
519 IHF. If the choice of the interrupt routing model is not known to the SPD
520 service at compile time, then the SP should pass this information to the SPD
536    by exporting a separate entrypoint for Secure-EL1 interrupts to the SPD
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
561    allocate a function identifier to issue a SMC64 or SMC32 to the SPD
563    non-secure interrupt. If this function identifier is not known to the SPD
572    have not effect. The SPD service should register a non-secure interrupt
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
694    generated according to the interrupt routing model specified by the SPD
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
731    another higher priority Secure-EL1 interrupt or a EL3 interrupt. The SPD
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
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.
925 when a non-secure interrupt is generated, the SP should coordinate with the SPD