Hi @ioannisg,
FYI. Feder is on holiday and will back to office on 10th May.
Thanks.

Assigned to Ken for the warning fix.

Thanks, Kevin.

Hi @RobertRostohar ,
All issues are closed. The crypto header issue should follow up in mbedcrypto changes, not in TF-M as we have aligned.
So I'm going to close this root issue.
Please let me know if you have any question.

Had the workshop and aligned the solution for this issue.
The changes are made and verified locally for CMSIS Pack.
Next step is to upstream the solution to mbedCrypto.
As it's not TF-M issue anymore, so close this issue.

Hi @jf549
Any update for this ticket?

Yes, the TZ API is not widely supported and the RTOSes which support v8m TZ are inventing their own "TZ" API for secure context switch (e.g. FreeRTOS). So, we intended to make the "Secure Context Management" ecosystem more aligned. For example, we are also introducing TZ API in RT-Thread.
But you're right, it's optional if there's no multiple secure context in TF-M. The value of NS client ID and NS access policy are use case specific. We provide the way to support that but it should be optional.
We will check if anything will go wrong if RTOS doesn't call the TZ API to TF-M. If we found issues, then will fix them.
Thanks for the valuable input!

In T615#7152, @ReinhardKeil wrote:

This is related to https://lists.trustedfirmware.org/pipermail/tf-m/2019-December/000581.html.
Pictures are filed here as the email list does not support pictures.

@kevin-peng-hao can you update some progress?

Working on the proposal.

@kevin-peng-hao has sent out the design in TF-M mailing list for review. Please check @ademars .

@KenLSoft will look at the UART interrupt support in SVC issue.

Fixed and merged the patch https://review.trustedfirmware.org/c/trusted-firmware-m/+/2335