CSS: Reorganize the SCP Image transfer functionality
The SCP_BL2 is transferred to SCP during BL2 image load and authenticate
sequence. The Boot-Over-MHU (BOM) protocol is used as transport for this. After
the SCP boots using the transferred image, the AP CPU waits till the `READY`
message is received from SCP. This patch separates the API for transport of
image from the wait for `READY` message and also moves the related files to
the `css/drivers` folder. The previous API `scp_bootloader_transfer` is
renamed to `css_scp_boot_image_xfer` to reflect the css naming convention.
This reorganisation also allows easier switch to a different transport
(eg: Shared Data Structure based transfer) in future

Change-Id: I8a96f9c4616ffde6dbfdf7c18f6f6f8bfa40bbf0
Signed-off-by: Soby Mathew <soby.mathew@arm.com>
1 parent 6c401f3 commit 74d44a49f89efc02decda22d075276a8a763be45
@Soby Mathew Soby Mathew authored on 3 May 2017
Showing 8 changed files
View
plat/arm/css/common/css_bl2_setup.c
View
plat/arm/css/common/css_bl2u_setup.c
View
plat/arm/css/common/css_common.mk
View
plat/arm/css/common/css_scp_bootloader.c 100644 → 0
View
plat/arm/css/common/css_scp_bootloader.h 100644 → 0
View
plat/arm/css/drivers/scp/css_bom_bootloader.c 0 → 100644
View
plat/arm/css/drivers/scp/css_scp.h
View
plat/arm/css/drivers/scpi/css_scpi.h