Integrate routing extension into existing SPs
The RPC layer uses the SP messaging layer with the routing extension
enabled thus it makes SPs able to make or forward return channel calls.
Change-Id: Id359b0e570702404ef0151697436d454eb950e44
Signed-off-by: Imre Kis <imre.kis@arm.com>
diff --git a/deployments/sfs-demo/opteesp/sp.c b/deployments/sfs-demo/opteesp/sp.c
index 1d8fe87..1f049ae 100644
--- a/deployments/sfs-demo/opteesp/sp.c
+++ b/deployments/sfs-demo/opteesp/sp.c
@@ -11,6 +11,7 @@
#include <service/secure_storage/backend/secure_storage_client/secure_storage_client.h>
#include <psa/internal_trusted_storage.h>
#include <sp_api.h>
+#include "sp_messaging.h"
#include <sp_rxtx.h>
#include <trace.h>
#include <string.h>
@@ -131,7 +132,7 @@
ffa_result ffa_res;
sp_result sp_res;
- struct ffa_direct_msg req_msg;
+ struct sp_msg req_msg = { 0 };
struct rpc_caller *caller;
struct ffarpc_caller ffa_caller;
struct secure_storage_client secure_storage_client;
@@ -181,7 +182,7 @@
}
/* End of boot phase */
- ffa_msg_wait(&req_msg);
+ sp_msg_wait(&req_msg);
err:
EMSG("Test SP error");