Hi Peng
I've just joined this mailing list after being pointed to this thread.
As ARM Trusted Firmware (TF) tech lead, I strongly encourage option 3, assuming you mean using the standalone AArch32 PSCI library provided in the upstream TF code base.
If by Option 1 you mean a full port of TF to AArch32, we consider this not feasible due to the architectural limitations that Jens described in his mail earlier. These limitations are also described in the presentation I gave at the last Linaro Connect in Las Vegas.
Option 2 is going to be equally challenging. Apart from being very difficult, there would be very tight coupling between U-Boot and OP-TEE, which may not be desirable for OP-TEE.
It's true that TF AArch32 support is currently focussed on ARMv8-A AArch32 support, but adding support for ARMv7-A is not a major task. We just need some help from the TF community to implement this.
In terms of implementing Option 3, Joakim mentioned looking into this early next year. We too were thinking of looking into this around the same time. I echo his comments around you helping with this if you want. We (ARM) are happy to provide consultancy.
In any case, we should agree among ourselves what the plan is before anyone embarks on this work!
Regards
Dan.
On 11 November 2016 at 10:21, Peng Fan <peng.fan at nxp.comhttps://lists.linaro.org/mailman/listinfo/tee-dev> wrote:
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.
Option2, requires some efforts. And needs some wrap code between uboot monitor code and TEE and Linux.
Actually I prefer option3, and secondary cores can be booted up with psci in OP-TEE. Before I
put more efforts, I would like to ask whether this is acceptable from OP-TEE community.
Thanks,
Peng.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Dan,
Thanks for your reply.
I thought option2 maybe a good choice, but ARMv7 does not have EL3 as v8, so needs a tight coupling between U-Boot and TEE which is not good. We want to make TEE an optional component in our software, but seems only option3 is acceptable now.
Thanks, Peng.
From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Dan Handley Sent: Tuesday, November 15, 2016 3:49 AM To: tee-dev@lists.linaro.org Subject: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng
I've just joined this mailing list after being pointed to this thread.
As ARM Trusted Firmware (TF) tech lead, I strongly encourage option 3, assuming you mean using the standalone AArch32 PSCI library provided in the upstream TF code base.
If by Option 1 you mean a full port of TF to AArch32, we consider this not feasible due to the architectural limitations that Jens described in his mail earlier. These limitations are also described in the presentation I gave at the last Linaro Connect in Las Vegas.
Option 2 is going to be equally challenging. Apart from being very difficult, there would be very tight coupling between U-Boot and OP-TEE, which may not be desirable for OP-TEE.
It's true that TF AArch32 support is currently focussed on ARMv8-A AArch32 support, but adding support for ARMv7-A is not a major task. We just need some help from the TF community to implement this.
In terms of implementing Option 3, Joakim mentioned looking into this early next year. We too were thinking of looking into this around the same time. I echo his comments around you helping with this if you want. We (ARM) are happy to provide consultancy.
In any case, we should agree among ourselves what the plan is before anyone embarks on this work!
Regards
Dan.
On 11 November 2016 at 10:21, Peng Fan <peng.fan at nxp.comhttps://lists.linaro.org/mailman/listinfo/tee-dev> wrote:
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.
Option2, requires some efforts. And needs some wrap code between uboot monitor code and TEE and Linux.
Actually I prefer option3, and secondary cores can be booted up with psci in OP-TEE. Before I
put more efforts, I would like to ask whether this is acceptable from OP-TEE community.
Thanks,
Peng.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Peng
You may be in luck. Trusted Firmware provides a minimal Secure Payload called SP_MIN, which integrates the PSCI library into a minimal secure monitor, without any TEE functionality: https://github.com/ARM-software/arm-trusted-firmware/tree/master/bl32/sp_min
This is requires a little bit of porting work for each platform. The port to ARM's development platforms can be found here: https://github.com/ARM-software/arm-trusted-firmware/tree/master/plat/arm/co...
Due to the architecture, I think all AArch32 options require a tight coupling between the TEE (if any), monitor and PSCI implementation.
I hope that helps
Regards
Dan.
From: Peng Fan [mailto:peng.fan@nxp.com] Sent: 15 November 2016 01:01 To: Dan Handley; tee-dev@lists.linaro.org Cc: Nitin Garg; Jason Liu; Anson Huang Subject: RE: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Dan,
Thanks for your reply.
I thought option2 maybe a good choice, but ARMv7 does not have EL3 as v8, so needs a tight coupling between U-Boot and TEE which is not good. We want to make TEE an optional component in our software, but seems only option3 is acceptable now.
Thanks, Peng.
From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Dan Handley Sent: Tuesday, November 15, 2016 3:49 AM To: tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Subject: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng
I've just joined this mailing list after being pointed to this thread.
As ARM Trusted Firmware (TF) tech lead, I strongly encourage option 3, assuming you mean using the standalone AArch32 PSCI library provided in the upstream TF code base.
If by Option 1 you mean a full port of TF to AArch32, we consider this not feasible due to the architectural limitations that Jens described in his mail earlier. These limitations are also described in the presentation I gave at the last Linaro Connect in Las Vegas.
Option 2 is going to be equally challenging. Apart from being very difficult, there would be very tight coupling between U-Boot and OP-TEE, which may not be desirable for OP-TEE.
It's true that TF AArch32 support is currently focussed on ARMv8-A AArch32 support, but adding support for ARMv7-A is not a major task. We just need some help from the TF community to implement this.
In terms of implementing Option 3, Joakim mentioned looking into this early next year. We too were thinking of looking into this around the same time. I echo his comments around you helping with this if you want. We (ARM) are happy to provide consultancy.
In any case, we should agree among ourselves what the plan is before anyone embarks on this work!
Regards
Dan.
On 11 November 2016 at 10:21, Peng Fan <peng.fan at nxp.comhttps://lists.linaro.org/mailman/listinfo/tee-dev> wrote:
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.
Option2, requires some efforts. And needs some wrap code between uboot monitor code and TEE and Linux.
Actually I prefer option3, and secondary cores can be booted up with psci in OP-TEE. Before I
put more efforts, I would like to ask whether this is acceptable from OP-TEE community.
Thanks,
Peng.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Dan,
Thanks for the info. Because of the hardware limitation, I tend to implement psci in TEE which needs less efforts. Anyway I still wonder whether you or Joakim have any plan to implement TEE support in ATF for Aarch32.
Thanks, Peng.
From: Dan Handley [mailto:Dan.Handley@arm.com] Sent: Tuesday, November 15, 2016 5:11 PM To: Peng Fan peng.fan@nxp.com; tee-dev@lists.linaro.org Cc: Nitin Garg nitin.garg@nxp.com; Jason Liu jason.hui.liu@nxp.com; Anson Huang anson.huang@nxp.com Subject: RE: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng
You may be in luck. Trusted Firmware provides a minimal Secure Payload called SP_MIN, which integrates the PSCI library into a minimal secure monitor, without any TEE functionality: https://github.com/ARM-software/arm-trusted-firmware/tree/master/bl32/sp_min
This is requires a little bit of porting work for each platform. The port to ARM's development platforms can be found here: https://github.com/ARM-software/arm-trusted-firmware/tree/master/plat/arm/co...
Due to the architecture, I think all AArch32 options require a tight coupling between the TEE (if any), monitor and PSCI implementation.
I hope that helps
Regards
Dan.
From: Peng Fan [mailto:peng.fan@nxp.com] Sent: 15 November 2016 01:01 To: Dan Handley; tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Cc: Nitin Garg; Jason Liu; Anson Huang Subject: RE: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Dan,
Thanks for your reply.
I thought option2 maybe a good choice, but ARMv7 does not have EL3 as v8, so needs a tight coupling between U-Boot and TEE which is not good. We want to make TEE an optional component in our software, but seems only option3 is acceptable now.
Thanks, Peng.
From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Dan Handley Sent: Tuesday, November 15, 2016 3:49 AM To: tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Subject: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng
I've just joined this mailing list after being pointed to this thread.
As ARM Trusted Firmware (TF) tech lead, I strongly encourage option 3, assuming you mean using the standalone AArch32 PSCI library provided in the upstream TF code base.
If by Option 1 you mean a full port of TF to AArch32, we consider this not feasible due to the architectural limitations that Jens described in his mail earlier. These limitations are also described in the presentation I gave at the last Linaro Connect in Las Vegas.
Option 2 is going to be equally challenging. Apart from being very difficult, there would be very tight coupling between U-Boot and OP-TEE, which may not be desirable for OP-TEE.
It's true that TF AArch32 support is currently focussed on ARMv8-A AArch32 support, but adding support for ARMv7-A is not a major task. We just need some help from the TF community to implement this.
In terms of implementing Option 3, Joakim mentioned looking into this early next year. We too were thinking of looking into this around the same time. I echo his comments around you helping with this if you want. We (ARM) are happy to provide consultancy.
In any case, we should agree among ourselves what the plan is before anyone embarks on this work!
Regards
Dan.
On 11 November 2016 at 10:21, Peng Fan <peng.fan at nxp.comhttps://lists.linaro.org/mailman/listinfo/tee-dev> wrote:
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.
Option2, requires some efforts. And needs some wrap code between uboot monitor code and TEE and Linux.
Actually I prefer option3, and secondary cores can be booted up with psci in OP-TEE. Before I
put more efforts, I would like to ask whether this is acceptable from OP-TEE community.
Thanks,
Peng.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Peng
I'm not sure what you mean by "TEE support in ATF for Aarch32". We've already provided PSCI support in TF for AArch32, for integration into TEEs. As I said before, both Joakim's team and mine are interested in integrating this PSCI support into OP-TEE early next year, but we haven't committed to this yet. I'm not sure what more support in TF you are expecting?
Regards
Dan.
From: Peng Fan [mailto:peng.fan@nxp.com] Sent: 15 November 2016 12:30 To: Dan Handley; tee-dev@lists.linaro.org Cc: Nitin Garg; Jason Liu; Anson Huang Subject: RE: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Dan,
Thanks for the info. Because of the hardware limitation, I tend to implement psci in TEE which needs less efforts. Anyway I still wonder whether you or Joakim have any plan to implement TEE support in ATF for Aarch32.
Thanks, Peng.
From: Dan Handley [mailto:Dan.Handley@arm.com] Sent: Tuesday, November 15, 2016 5:11 PM To: Peng Fan <peng.fan@nxp.commailto:peng.fan@nxp.com>; tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Cc: Nitin Garg <nitin.garg@nxp.commailto:nitin.garg@nxp.com>; Jason Liu <jason.hui.liu@nxp.commailto:jason.hui.liu@nxp.com>; Anson Huang <anson.huang@nxp.commailto:anson.huang@nxp.com> Subject: RE: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng
You may be in luck. Trusted Firmware provides a minimal Secure Payload called SP_MIN, which integrates the PSCI library into a minimal secure monitor, without any TEE functionality: https://github.com/ARM-software/arm-trusted-firmware/tree/master/bl32/sp_min
This is requires a little bit of porting work for each platform. The port to ARM's development platforms can be found here: https://github.com/ARM-software/arm-trusted-firmware/tree/master/plat/arm/co...
Due to the architecture, I think all AArch32 options require a tight coupling between the TEE (if any), monitor and PSCI implementation.
I hope that helps
Regards
Dan.
From: Peng Fan [mailto:peng.fan@nxp.com] Sent: 15 November 2016 01:01 To: Dan Handley; tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Cc: Nitin Garg; Jason Liu; Anson Huang Subject: RE: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Dan,
Thanks for your reply.
I thought option2 maybe a good choice, but ARMv7 does not have EL3 as v8, so needs a tight coupling between U-Boot and TEE which is not good. We want to make TEE an optional component in our software, but seems only option3 is acceptable now.
Thanks, Peng.
From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Dan Handley Sent: Tuesday, November 15, 2016 3:49 AM To: tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Subject: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng
I've just joined this mailing list after being pointed to this thread.
As ARM Trusted Firmware (TF) tech lead, I strongly encourage option 3, assuming you mean using the standalone AArch32 PSCI library provided in the upstream TF code base.
If by Option 1 you mean a full port of TF to AArch32, we consider this not feasible due to the architectural limitations that Jens described in his mail earlier. These limitations are also described in the presentation I gave at the last Linaro Connect in Las Vegas.
Option 2 is going to be equally challenging. Apart from being very difficult, there would be very tight coupling between U-Boot and OP-TEE, which may not be desirable for OP-TEE.
It's true that TF AArch32 support is currently focussed on ARMv8-A AArch32 support, but adding support for ARMv7-A is not a major task. We just need some help from the TF community to implement this.
In terms of implementing Option 3, Joakim mentioned looking into this early next year. We too were thinking of looking into this around the same time. I echo his comments around you helping with this if you want. We (ARM) are happy to provide consultancy.
In any case, we should agree among ourselves what the plan is before anyone embarks on this work!
Regards
Dan.
On 11 November 2016 at 10:21, Peng Fan <peng.fan at nxp.comhttps://lists.linaro.org/mailman/listinfo/tee-dev> wrote:
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.
Option2, requires some efforts. And needs some wrap code between uboot monitor code and TEE and Linux.
Actually I prefer option3, and secondary cores can be booted up with psci in OP-TEE. Before I
put more efforts, I would like to ask whether this is acceptable from OP-TEE community.
Thanks,
Peng.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you. IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Peng,
Sorry for late response. Earlier we had discussions with Joakim about PSCI ARM32 support in OP-TEE. PFA mail-chain.
So, I have worked on integrating PSCI ARM32 in OP-TEE on top of rel 2.0.0 (Option 3). Actually I had prepared draft set of patches for the same but project was put on hold so could not send RFC patches.
PFA draft version of patch-set for PSCI ARM32 support in OP-TEE on top of rel 2.0.0.
Following PSCI features were tested on LS1021ATWR platform (plat-ls): 1. PSCI_VERSION
2. PSCI_CPU_ON
3. PSCI_CPU_OFF
4. PSCI_AFFINITY_INFO
5. PSCI_SYSTEM_OFF
6. PSCI_SYSTEM_RESET
I hope this patch-set will help you while integrating PSCI ARM32 in OP-TEE on latest upstream code.
Regards, Sumit
From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Peng Fan Sent: Tuesday, November 15, 2016 6:31 AM To: Dan Handley Dan.Handley@arm.com; tee-dev@lists.linaro.org Cc: Nitin Garg nitin.garg@nxp.com; Anson Huang anson.huang@nxp.com; Jason Liu jason.hui.liu@nxp.com Subject: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Dan,
Thanks for your reply.
I thought option2 maybe a good choice, but ARMv7 does not have EL3 as v8, so needs a tight coupling between U-Boot and TEE which is not good. We want to make TEE an optional component in our software, but seems only option3 is acceptable now.
Thanks, Peng.
From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Dan Handley Sent: Tuesday, November 15, 2016 3:49 AM To: tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Subject: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng
I've just joined this mailing list after being pointed to this thread.
As ARM Trusted Firmware (TF) tech lead, I strongly encourage option 3, assuming you mean using the standalone AArch32 PSCI library provided in the upstream TF code base.
If by Option 1 you mean a full port of TF to AArch32, we consider this not feasible due to the architectural limitations that Jens described in his mail earlier. These limitations are also described in the presentation I gave at the last Linaro Connect in Las Vegas.
Option 2 is going to be equally challenging. Apart from being very difficult, there would be very tight coupling between U-Boot and OP-TEE, which may not be desirable for OP-TEE.
It's true that TF AArch32 support is currently focussed on ARMv8-A AArch32 support, but adding support for ARMv7-A is not a major task. We just need some help from the TF community to implement this.
In terms of implementing Option 3, Joakim mentioned looking into this early next year. We too were thinking of looking into this around the same time. I echo his comments around you helping with this if you want. We (ARM) are happy to provide consultancy.
In any case, we should agree among ourselves what the plan is before anyone embarks on this work!
Regards
Dan.
On 11 November 2016 at 10:21, Peng Fan <peng.fan at nxp.comhttps://lists.linaro.org/mailman/listinfo/tee-dev> wrote:
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.
Option2, requires some efforts. And needs some wrap code between uboot monitor code and TEE and Linux.
Actually I prefer option3, and secondary cores can be booted up with psci in OP-TEE. Before I
put more efforts, I would like to ask whether this is acceptable from OP-TEE community.
Thanks,
Peng.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
Hi Sumit,
I already have basic psci function working in TEE. Anyway thanks, I'll look into your patches.
Thanks, Peng.
From: Sumit Garg Sent: Tuesday, November 15, 2016 6:31 PM To: Peng Fan peng.fan@nxp.com; tee-dev@lists.linaro.org Cc: Nitin Garg nitin.garg@nxp.com; Anson Huang anson.huang@nxp.com; Jason Liu jason.hui.liu@nxp.com; Dan Handley Dan.Handley@arm.com; jens.wiklander@linaro.org; Joakim Bech joakim.bech@linaro.org; Ruchika Gupta ruchika.gupta@nxp.com Subject: RE: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng,
Sorry for late response. Earlier we had discussions with Joakim about PSCI ARM32 support in OP-TEE. PFA mail-chain.
So, I have worked on integrating PSCI ARM32 in OP-TEE on top of rel 2.0.0 (Option 3). Actually I had prepared draft set of patches for the same but project was put on hold so could not send RFC patches.
PFA draft version of patch-set for PSCI ARM32 support in OP-TEE on top of rel 2.0.0.
Following PSCI features were tested on LS1021ATWR platform (plat-ls): 1. PSCI_VERSION
2. PSCI_CPU_ON
3. PSCI_CPU_OFF
4. PSCI_AFFINITY_INFO
5. PSCI_SYSTEM_OFF
6. PSCI_SYSTEM_RESET
I hope this patch-set will help you while integrating PSCI ARM32 in OP-TEE on latest upstream code.
Regards, Sumit
From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Peng Fan Sent: Tuesday, November 15, 2016 6:31 AM To: Dan Handley <Dan.Handley@arm.commailto:Dan.Handley@arm.com>; tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Cc: Nitin Garg <nitin.garg@nxp.commailto:nitin.garg@nxp.com>; Anson Huang <anson.huang@nxp.commailto:anson.huang@nxp.com>; Jason Liu <jason.hui.liu@nxp.commailto:jason.hui.liu@nxp.com> Subject: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Dan,
Thanks for your reply.
I thought option2 maybe a good choice, but ARMv7 does not have EL3 as v8, so needs a tight coupling between U-Boot and TEE which is not good. We want to make TEE an optional component in our software, but seems only option3 is acceptable now.
Thanks, Peng.
From: Tee-dev [mailto:tee-dev-bounces@lists.linaro.org] On Behalf Of Dan Handley Sent: Tuesday, November 15, 2016 3:49 AM To: tee-dev@lists.linaro.orgmailto:tee-dev@lists.linaro.org Subject: Re: [Tee-dev] Introduce PSCI for OP-TEE ARM32
Hi Peng
I've just joined this mailing list after being pointed to this thread.
As ARM Trusted Firmware (TF) tech lead, I strongly encourage option 3, assuming you mean using the standalone AArch32 PSCI library provided in the upstream TF code base.
If by Option 1 you mean a full port of TF to AArch32, we consider this not feasible due to the architectural limitations that Jens described in his mail earlier. These limitations are also described in the presentation I gave at the last Linaro Connect in Las Vegas.
Option 2 is going to be equally challenging. Apart from being very difficult, there would be very tight coupling between U-Boot and OP-TEE, which may not be desirable for OP-TEE.
It's true that TF AArch32 support is currently focussed on ARMv8-A AArch32 support, but adding support for ARMv7-A is not a major task. We just need some help from the TF community to implement this.
In terms of implementing Option 3, Joakim mentioned looking into this early next year. We too were thinking of looking into this around the same time. I echo his comments around you helping with this if you want. We (ARM) are happy to provide consultancy.
In any case, we should agree among ourselves what the plan is before anyone embarks on this work!
Regards
Dan.
On 11 November 2016 at 10:21, Peng Fan <peng.fan at nxp.comhttps://lists.linaro.org/mailman/listinfo/tee-dev> wrote:
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.
Option2, requires some efforts. And needs some wrap code between uboot monitor code and TEE and Linux.
Actually I prefer option3, and secondary cores can be booted up with psci in OP-TEE. Before I
put more efforts, I would like to ask whether this is acceptable from OP-TEE community.
Thanks,
Peng.
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
-
Dan Handley -
Peng Fan -
Sumit Garg