Hi Alan,
This functionality looks like a privileged accessing and needs to be implemented in TF-M eventually. You can add a support for this and upstream back to TF-M if you have already started working on it.
For convention of platform SVC, we need to collect more requirements and user cases to see if it is necessary. If a partition acts as a driver, it can access the peripheral by assign memory mapped range in manifest; and they could use your 'privileged accessing' SVC for accessing privileged registers. And it could involve interrupt module if it needs to handle interrupts. It does not need to face the NVIC setting itself in concept.
BR
-Ken
-----Original Message----- From: DeMars, Alan ademars@ti.com Sent: Friday, July 26, 2019 10:18 AM To: Ken Liu (Arm Technology China) Ken.Liu@arm.com Cc: tf-m@lists.trustedfirmware.org; nd nd@arm.com Subject: Re: [EXTERNAL] RE: Adding a platform specific tfm_svc_number_t
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