Allow BL3-2 platform definitions to be optional
authorDan Handley <dan.handley@arm.com>
Tue, 15 Apr 2014 10:38:38 +0000 (11:38 +0100)
committerAndrew Thoelke <andrew.thoelke@arm.com>
Thu, 22 May 2014 22:15:36 +0000 (23:15 +0100)
commit1151c82101eb3cb2472d3b513f0c828ad098b13c
treed98c5e19feaecdb4c970ce160caa1a9bed35f9ea
parentdbad1bacba0a7adfd3c7c559f0fd0805087aeddd
Allow BL3-2 platform definitions to be optional

The generic image loading and IO FIP code no longer forces the
platform to create BL3-2 (Secure-EL1 Payload) specific
definitions. The BL3-2 loading code in bl2/bl2main.c is wrapped
by a #ifdef BL32_BASE blocks, allowing the BL3-2 definitions to
be optional. Similarly for the name_uuid array defintion in
drivers/io/io_fip.c.

Also update the porting guide to reflect this change.

The BL3-2 platform definitions remain non-configurably present
in the FVP port.

Fixes ARM-software/tf-issues#68

Change-Id: Iea28b4e94d87a31f5522f271e290919a8a955460
bl2/bl2_main.c
docs/porting-guide.md
drivers/io/io_fip.c