search

ARM-software / tf-issues

Issue tracking for the ARM Trusted Firmware project
37 stars 16 forks source link

nobody call bl31_set_next_image_type() now? #162

Closed chinamao closed 10 years ago

chinamao commented 10 years ago

as title

athoelke commented 10 years ago

There are two basic ways that a SPD service can initialise the secure payload (BL3-2) that are described in the design documentation.

At present the TSPD uses the second approach, where BL3-2 is initialised synchronously during tspd_init().

bl31_set_next_image_type() would be required for a SPD to use the first approach, where the exit from EL3 in bl31_main() is to BL3-2. When BL3-2 signals completion of initialisation to the SPD this switches to the normal world and prepares for exiting EL3 into BL3-3.