Thanks for your reply vlad.

Our processor is arm cortex A5. It supports armv7-A instruction set.According to you , we don't need to bother about trusted firmware.

And we are not using standard arm gic interrupt controller , we are using custom interrupt controller.

How much porting effort should be there as we are not using gic?

Can you please suggest me any reference for cortex A5(armvV7a) for understanding.

Thanks.

From: Volodymyr Babchuk <vlad.babchuk@gmail.com>
Sent: Thursday, October 6, 2016 7:04:45 PM
To: Siva Krishna Reddy Yaramala
Cc: tee-dev@lists.linaro.org
Subject: Re: [Tee-dev] OPtee Porting.

Hi Siva,

On 6 October 2016 at 15:03, Siva Krishna Reddy Yaramala
<SivaKrishnaReddy.Yaramala@inedasystems.com> wrote:

> Is arm-trusted firmware really required in the optee bringup?
arm trusted firmware is a standard component on ARMv8 architecture. It
is unavailable on ARMv7. On ARMv7 OP-TEE works as standalone secure
monitor (without ARM TF).
Technically you can throw away ARM TF on ARMv8 and use OP-TEE in
standalone mode. You will need some changes in optee in this case.
AFAIK no one did this before.

> Can we boot optee directly from u-boot without arm-trusted firmware?
Usually op-tee boots before u-boot. But it is platform dependent. If
u-boot on your platform boots in EL3 (secure monitor) mode, then, yes,
you can boot optee from u-boot.
But usually u-boot operates in EL1 (supervisor) mode, so it is too
late to boot up op-tee. Also, in case of booting optee from u-boot you
need to develop a way to return back to u-boot to boot linux kernel.

> Is there any specific hardware requirements to run optee?
Processor core need to support ARM Security Extensions. This is only
one hardware requirement.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________