For example, I need a function to trigger an interrupt mapped to the non-secure domain. In non privileged thread mode, writing to the NVIC registers is forbidden. Therefore I need to define a function that will trap into SVC handler mode to perform that action.
Alan
On Jul 25, 2019, at 6:49 PM, Ken Liu (Arm Technology China) Ken.Liu@arm.com wrote:
Hi Alan, Can you share us your usage details? This could help us on defining the svc number things you mentioned.
Thanks.
-Ken
-----Original Message----- From: TF-M tf-m-bounces@lists.trustedfirmware.org On Behalf Of DeMars, Alan via TF-M Sent: Friday, July 26, 2019 6:59 AM To: tf-m@lists.trustedfirmware.org Subject: [TF-M] Adding a platform specific tfm_svc_number_t
I need to define platform specific SPM APIs that will be invoked by our SPs.
Is there a convention for 'cleanly' adding platform specific SVC enumerations to the tfm_svc_number_t typedef in tfm_svc.h as well as platform specific 'case's to SVCHandler_main() and/or SVC_Handler_IPC()?
Alan
-- TF-M mailing list TF-M@lists.trustedfirmware.org https://lists.trustedfirmware.org/mailman/listinfo/tf-m