Change Details

We have APIs for our SP services that must be executed in Secure Privileged mode. Currently, the set of SVC handlers is entirely within the tfm core code base. I propose a simple mechanism for extending the set of SVCs to include platform specific functions. To enable platform specific SVC handlers, add “–DPLATFOM_SVC_HANDLERS” to the CMAKE command line. User must then provide an implementation of: int32_t platform_svc_handlers(tfm_svc_number_t svc_num, uint32_t *ctx, uint32_t lr); The platform specific SVC handler enumerations will begin with the new enumeration value "TFM_SVC_PLATFORM_BASE".

We have APIs for our SP services that must be executed in Secure Privileged mode. Currently, the set of SVC handlers is entirely within the tfm core code base. I propose a simple mechanism for extending the set of SVCs to include platform specific functions. To enable platform specific SVC handlers, add “–DPLATFORM_SVC_HANDLERS=True” to the CMAKE command line. When PLATFORM_SVC_HANDLERS is defined, the user must then provide an implementation of: int32_t platform_svc_handlers(tfm_svc_number_t svc_num, uint32_t *ctx, uint32_t lr); The platform specific SVC handler enumerations will begin with the new enumeration value "TFM_SVC_PLATFORM_BASE".

We have APIs for our SP services that must be executed in Secure Privileged mode. Currently, the set of SVC handlers is entirely within the tfm core code base. I propose a simple mechanism for extending the set of SVCs to include platform specific functions. To enable platform specific SVC handlers, add “–DPLATFORM_SVC_HANDLERS”=True” to the CMAKE command line. User When PLATFORM_SVC_HANDLERS is defined, the user must then provide an implementation of: int32_t platform_svc_handlers(tfm_svc_number_t svc_num, uint32_t *ctx, uint32_t lr); The platform specific SVC handler enumerations will begin with the new enumeration value "TFM_SVC_PLATFORM_BASE".