I haven't looked at in much detail but I think the shareability attributes would need to be exposed by the mm module, and then converted by ffa_memory_permissions_to_mode.

Persistent key support has been added as part of TFMv1.1. Clsoing this issue.

SMMUv3.2 supports secure Stage-2 translations and that's the feature we intend to enable as a first step.
The IP also supports "nested translations" aka S-EL1 SMMU paravirtualization although we're not looking at this option immediately.

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5775

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5759

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5695
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5696
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5697
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5698
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5699

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5669

Description: 'Short circuit signature test of attest token'

Test logs:

Thanks for your reply, so there is Stage-2 SMMU support, right? And i think we can support passthrough io support in Secure-EL1 with Stage-2 SMMU

Notes, missing features for current uploaded source changes:
• No support for isolation level2 on SSE-200
• Protected Storage is an Application RoT partition, but PS also moved to Secure Enclave
• Some regression tests running on secure side of SSE-200 fail as all messages are forwarded with the same client ID to Secure Enclave
• All IPC message forwarding is a blocking call
• Only one message is put into the mailbox at a time
• Musca-B1 related documentation is not complete yet
• Generated files are not committed, manifest parser should be run before build.
• The BL0 component mentioned in the tech forum presentation is not uploaded, as it is based on the new cmake system, and not so interesting right now
• Cmake changes are rudimentary, will be rebased to new cmake system.

This does not seem to be an issue with the new build system.

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5609

Patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5598

The patches are merged.

The change is merged.

We're considering the SMMUv3.2 support which covers the Secure Stage-2 mappings (https://developer.arm.com/documentation/ihi0070/latest).
This is still in initial investigation phases, but we hope to share design details and early patches by end of Q4'20.

Several preparation patches including scatter file adjustments.
Starts with:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5571

Several patches for adjusting the manifests:
https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/5567
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5568
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5569

Patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5566

@odeprez / Arm might be able to comment on this.

Related review:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5519

patch link:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5548

patch link:
https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/5498
https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/5528

Another side patch:
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5497

patch link: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5492

The fix for this issue had been merged.

Got it! Thanks for sharing such info... I concur that innovation is our companion. It encourages us to do things we have to manage, facilitate our lives. Concerning me I downloaded https://topspying.com/spy-on-a-cell-phone-without-accessing-it/ not to stress over the individual existence of my kids. You know, they are youthful and others may exploit them, so I don't imagine that spy on their mobile phones is the most exceedingly awful thought. I'm understanding when I'm getting to their own information and see that it is nothing to stress over

what about SMMUV3.x ?

Attaching the test logs running the regression configurations:

Attaching the logs applying the changes and running the regression configs:
For Musca-S1:

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/706
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5460/
https://review.trustedfirmware.org/c/TF-M/tf-m-tests/+/5461

Patch for fix: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5457

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5405
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5406

https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5448

I've tested the scripts on OS X by changing readlink to greadlink (available via brew install coreutils), since the OS X system readlink doesn't support the -f option, and this works fine on OS X. A simple platform check is required to two of the scripts, similar to what you see here: https://git.trustedfirmware.org/TF-M/trusted-firmware-m.git/tree/platform/ext/target/nxp/lpcxpresso55s69/scripts/build.sh#n11

Change for this issue: https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/5443