|
|
|
|
/*
|
|
|
|
|
* Copyright (c) 2013-2017, ARM Limited and Contributors. All rights reserved.
|
|
|
|
|
*
|
|
|
|
|
* SPDX-License-Identifier: BSD-3-Clause
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#include <arch.h>
|
|
|
|
|
#include <el3_common_macros.S>
|
|
|
|
|
|
|
|
|
|
.globl bl1_entrypoint
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
/* -----------------------------------------------------
|
|
|
|
|
* bl1_entrypoint() is the entry point into the trusted
|
|
|
|
|
* firmware code when a cpu is released from warm or
|
|
|
|
|
* cold reset.
|
|
|
|
|
* -----------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
func bl1_entrypoint
|
|
|
|
|
/* ---------------------------------------------------------------------
|
|
|
|
|
* If the reset address is programmable then bl1_entrypoint() is
|
|
|
|
|
* executed only on the cold boot path. Therefore, we can skip the warm
|
|
|
|
|
* boot mailbox mechanism.
|
|
|
|
|
* ---------------------------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
el3_entrypoint_common \
|
|
|
|
|
_init_sctlr=1 \
|
|
|
|
|
_warm_boot_mailbox=!PROGRAMMABLE_RESET_ADDRESS \
|
|
|
|
|
_secondary_cold_boot=!COLD_BOOT_SINGLE_CPU \
|
|
|
|
|
_init_memory=1 \
|
|
|
|
|
_init_c_runtime=1 \
|
|
|
|
|
_exception_vectors=bl1_exceptions
|
|
|
|
|
|
|
|
|
|
/* ---------------------------------------------
|
|
|
|
|
* Architectural init. can be generic e.g.
|
|
|
|
|
* enabling stack alignment and platform spec-
|
|
|
|
|
* ific e.g. MMU & page table setup as per the
|
|
|
|
|
* platform memory map. Perform the latter here
|
|
|
|
|
* and the former in bl1_main.
|
|
|
|
|
* ---------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
bl bl1_early_platform_setup
|
|
|
|
|
bl bl1_plat_arch_setup
|
|
|
|
|
|
|
|
|
|
/* --------------------------------------------------
|
|
|
|
|
* Initialize platform and jump to our c-entry point
|
Add descriptor based image management support in BL1
As of now BL1 loads and execute BL2 based on hard coded information
provided in BL1. But due to addition of support for upcoming Firmware
Update feature, BL1 now require more flexible approach to load and
run different images using information provided by the platform.
This patch adds new mechanism to load and execute images based on
platform provided image id's. BL1 now queries the platform to fetch
the image id of the next image to be loaded and executed. In order
to achieve this, a new struct image_desc_t was added which holds the
information about images, such as: ep_info and image_info.
This patch introduces following platform porting functions:
unsigned int bl1_plat_get_next_image_id(void);
This is used to identify the next image to be loaded
and executed by BL1.
struct image_desc *bl1_plat_get_image_desc(unsigned int image_id);
This is used to retrieve the image_desc for given image_id.
void bl1_plat_set_ep_info(unsigned int image_id,
struct entry_point_info *ep_info);
This function allows platforms to update ep_info for given
image_id.
The plat_bl1_common.c file provides default weak implementations of
all above functions, the `bl1_plat_get_image_desc()` always return
BL2 image descriptor, the `bl1_plat_get_next_image_id()` always return
BL2 image ID and `bl1_plat_set_ep_info()` is empty and just returns.
These functions gets compiled into all BL1 platforms by default.
Platform setup in BL1, using `bl1_platform_setup()`, is now done
_after_ the initialization of authentication module. This change
provides the opportunity to use authentication while doing the
platform setup in BL1.
In order to store secure/non-secure context, BL31 uses percpu_data[]
to store context pointer for each core. In case of BL1 only the
primary CPU will be active hence percpu_data[] is not required to
store the context pointer.
This patch introduce bl1_cpu_context[] and bl1_cpu_context_ptr[] to
store the context and context pointers respectively. It also also
re-defines cm_get_context() and cm_set_context() for BL1 in
bl1/bl1_context_mgmt.c.
BL1 now follows the BL31 pattern of using SP_EL0 for the C runtime
environment, to support resuming execution from a previously saved
context.
NOTE: THE `bl1_plat_set_bl2_ep_info()` PLATFORM PORTING FUNCTION IS
NO LONGER CALLED BY BL1 COMMON CODE. PLATFORMS THAT OVERRIDE
THIS FUNCTION MAY NEED TO IMPLEMENT `bl1_plat_set_ep_info()`
INSTEAD TO MAINTAIN EXISTING BEHAVIOUR.
Change-Id: Ieee4c124b951c2e9bc1c1013fa2073221195d881
9 years ago
|
|
|
* for this type of reset.
|
|
|
|
|
* --------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
bl bl1_main
|
Add descriptor based image management support in BL1
As of now BL1 loads and execute BL2 based on hard coded information
provided in BL1. But due to addition of support for upcoming Firmware
Update feature, BL1 now require more flexible approach to load and
run different images using information provided by the platform.
This patch adds new mechanism to load and execute images based on
platform provided image id's. BL1 now queries the platform to fetch
the image id of the next image to be loaded and executed. In order
to achieve this, a new struct image_desc_t was added which holds the
information about images, such as: ep_info and image_info.
This patch introduces following platform porting functions:
unsigned int bl1_plat_get_next_image_id(void);
This is used to identify the next image to be loaded
and executed by BL1.
struct image_desc *bl1_plat_get_image_desc(unsigned int image_id);
This is used to retrieve the image_desc for given image_id.
void bl1_plat_set_ep_info(unsigned int image_id,
struct entry_point_info *ep_info);
This function allows platforms to update ep_info for given
image_id.
The plat_bl1_common.c file provides default weak implementations of
all above functions, the `bl1_plat_get_image_desc()` always return
BL2 image descriptor, the `bl1_plat_get_next_image_id()` always return
BL2 image ID and `bl1_plat_set_ep_info()` is empty and just returns.
These functions gets compiled into all BL1 platforms by default.
Platform setup in BL1, using `bl1_platform_setup()`, is now done
_after_ the initialization of authentication module. This change
provides the opportunity to use authentication while doing the
platform setup in BL1.
In order to store secure/non-secure context, BL31 uses percpu_data[]
to store context pointer for each core. In case of BL1 only the
primary CPU will be active hence percpu_data[] is not required to
store the context pointer.
This patch introduce bl1_cpu_context[] and bl1_cpu_context_ptr[] to
store the context and context pointers respectively. It also also
re-defines cm_get_context() and cm_set_context() for BL1 in
bl1/bl1_context_mgmt.c.
BL1 now follows the BL31 pattern of using SP_EL0 for the C runtime
environment, to support resuming execution from a previously saved
context.
NOTE: THE `bl1_plat_set_bl2_ep_info()` PLATFORM PORTING FUNCTION IS
NO LONGER CALLED BY BL1 COMMON CODE. PLATFORMS THAT OVERRIDE
THIS FUNCTION MAY NEED TO IMPLEMENT `bl1_plat_set_ep_info()`
INSTEAD TO MAINTAIN EXISTING BEHAVIOUR.
Change-Id: Ieee4c124b951c2e9bc1c1013fa2073221195d881
9 years ago
|
|
|
|
|
|
|
|
/* --------------------------------------------------
|
|
|
|
|
* Do the transition to next boot image.
|
|
|
|
|
* --------------------------------------------------
|
|
|
|
|
*/
|
|
|
|
|
b el3_exit
|
|
|
|
|
endfunc bl1_entrypoint
|
