Djam/arm-trusted-firmware
1
0
Fork 0
mirror of https://github.com/ARM-software/arm-trusted-firmware.git synced 2025-04-25 14:25:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #485 from jcastillo-arm/jc/max_mmap_reg

Browse source 
Add 'MAX_MMAP_REGIONS' and 'ADDR_SPACE_SIZE' to the Porting Guide
This commit is contained in:
danh-arm 2016-01-13 12:40:31 +00:00
commit 6770d65ff5
1 changed files with 16 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
docs/porting-guide.md
View file

@ -413,6 +413,22 @@ constant must also be defined:
used, choose the smallest value needed to map the required virtual addresses used, choose the smallest value needed to map the required virtual addresses
for each BL stage. for each BL stage.
* **#define : MAX_MMAP_REGIONS**
Defines the maximum number of regions that are allocated by the translation
table library code. A region consists of physical base address, virtual base
address, size and attributes (Device/Memory, RO/RW, Secure/Non-Secure), as
defined in the `mmap_region_t` structure. The platform defines the regions
that should be mapped. Then, the translation table library will create the
corresponding tables and descriptors at runtime. To minimize the amount of
runtime memory used, choose the smallest value needed to register the
required regions for each BL stage.
* **#define : ADDR_SPACE_SIZE**
Defines the total size of the address space in bytes. For example, for a 32
bit address space, this value should be `(1ull << 32)`.
If the platform port uses the IO storage framework, the following constants If the platform port uses the IO storage framework, the following constants
must also be defined: must also be defined: