Hi, Bhupesh,
Which SoC are you preparing optee-demo for? I have i.MX 6UL and 7D porting for optee os and optee support in U-Boot.
Regards, Peng.
-----Original Message----- From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Sharma Bhupesh Sent: Thursday, July 23, 2015 12:30 PM To: tee-dev@lists.linaro.org Cc: Garg Sumit-B49020 Subject: [Tee-dev] ATF (or Secure-run-time firmware) flow during switch from tee-driver to tee-os on ARMv7 SoC
Hi TEE Experts,
We are trying to setup the optee-demo on a ARMv7 based Freescale SoC.
During the same, I noticed that the SMC calls from the optee-linux-driver directly land up on the optee-os side.
I was thinking that just like the ARMv8 flow, where the SMC handling should ideally be done by a Arm Trusted Firmware (or an equivalent secure-run-time firmware) agent running in EL3 privilege level, on ARMv7 too, if we have a resident ATF (or secure firmware) installed the SMC calls should be handled there.
In the opteep-design documentation can the references to SECURE MONITOR LAYER (see [1]) be assumed to be equivalent to a ATF like firmware.
Is this understanding correct or am I missing something here?
[1] https://github.com/OP-TEE/optee_os/blob/master/documentation/optee_design.md
Regards, Bhupesh _______________________________________________ Tee-dev mailing list Tee-dev@lists.linaro.org https://lists.linaro.org/mailman/listinfo/tee-dev