Hi,

the PPC configuration is reserved for the Secure world firmware only, especially for Secure Partition Manager HAL during boot up or during calls at runtime to enforce the security boundaries associated to each partition, hence these APIs are not exposed at all to the outside world, if we define outside outside as Non-Secure world or partitions themselves.

Relevant callers of the PPC driver are in each platform tfm_hal_isolation.c with implementations in target_cfg.c

Hope this helps

________________________________ From: Michael Khoyilar via TF-M tf-m@lists.trustedfirmware.org Sent: Friday, November 15, 2024 00:13 To: tf-m@lists.trustedfirmware.org tf-m@lists.trustedfirmware.org Subject: [TF-M] ARM PPC Driver invocation

Hi Team,

Thanks for you helps. This this time I want to know how does PPC functions will be called from application to set a possible feature? The question is how PPC functions are exposed to outside world? I know we have a common ARM API in under platform/ext/driver/Driver_PPC.h

I am mapping my PPCs to this API, however wondering how they might be called that refer to my specific PPCs ? I am not using the ARM naming for my PPCs drivers, for example not using the name Driver_AHB_PPCEXP0 (using the name Driver_APB_PPCBASE0). Thank you again.

Michael