Peng, Jerome,
On Fri, Nov 11, 2016 at 09:29:44PM +0100, Jerome Forissier wrote:
Le 11 nov. 2016 10:30 AM, "Peng Fan" peng.fan@nxp.com a écrit :
Hi,
I am trying to implement TEE and support Linux power features.
There are several options to include power features and TEE
ATFW for ARM32.
Develop runtime service code in U-Boot like ATFW.
Integrate PSCI ARM32 in OP-TEE.
Option1, ATFW seems not support ARM32, such as A9/A7. And the AArch32
support, I think(not sure), is not for legacy ARM32 cores.
Indeed it seems that the main focus is ARMv8-A. FYI, the presentation made by ARM at Linaro Connect is at http://connect.linaro.org/resource/las16/las16-402/.
Yes, we had a chat with ARM at Connect and currently it seems like their plans only cover ARMv8-A (I cannot tell whether that will change later on). Having that said we also discussed whether we (Linaro security team) could bring in the related functionality as a PSCI library into ARMv7-A. Due to the architectural differences between ARMv8-A and ARMv7-A, that would mean that we would need to bring the PSCI related code for ARMv7-A directly into the OP-TEE code base. I.e, we're talking about option three in Peng's proposal above. This is something we've put on our to-do list and would like to start looking into this cycle (which lasts until next Linaro Connect in Feb/March -17).
I don't think we will start the working until the beginning of next year. If you'd need it sooner than what I've described above, then I wouldn't mind of you start working and with this and champion this work (of course we would like to be in the loop, both assisting and for discussion).
Having that said, what benefits would there be going with proposal one or two instead of option three? If we could gather a list of pro's and cons, I think we can make a better decision about how to actually do this.