| /arm-trusted-firmware-2.8.0/plat/mediatek/lib/mtk_init/ |
| A D | mtk_mmap_init.c | 24 static void print_mmap(const mmap_region_t *regions) in print_mmap() argument
26 while (regions->size != 0U) { in print_mmap()
28 regions->base_va, in print_mmap()
29 regions->base_va + regions->size, in print_mmap()
30 regions->attr); in print_mmap()
31 regions++; in print_mmap()
38 const mmap_region_t *regions = bl_regions; in mtk_xlat_init() local
40 print_mmap(regions); in mtk_xlat_init()
46 regions = iter->mmap_ptr; in mtk_xlat_init()
49 print_mmap(regions); in mtk_xlat_init()
[all …]
|
| /arm-trusted-firmware-2.8.0/plat/common/ |
| A D | plat_bl_common.c | 116 const mmap_region_t *regions = bl_regions; in setup_page_tables() local
118 while (regions->size != 0U) { in setup_page_tables()
120 regions->base_va, in setup_page_tables()
121 regions->base_va + regions->size, in setup_page_tables()
122 regions->attr); in setup_page_tables()
123 regions++; in setup_page_tables()
|
| /arm-trusted-firmware-2.8.0/plat/rpi/rpi3/ |
| A D | rpi3_bl31_setup.c | 161 int i, regions, rc; in rpi3_dtb_add_mem_rsv() local
171 regions = fdt_num_mem_rsv(dtb); in rpi3_dtb_add_mem_rsv()
173 VERBOSE("rpi3: Found %d mem reserve region(s)\n", regions); in rpi3_dtb_add_mem_rsv()
176 if (regions < 1) in rpi3_dtb_add_mem_rsv()
184 for (i = 0; i < regions; i++) { in rpi3_dtb_add_mem_rsv()
201 if (i == regions) { in rpi3_dtb_add_mem_rsv()
|
| /arm-trusted-firmware-2.8.0/lib/utils/ |
| A D | mem_region.c | 56 void clear_map_dyn_mem_regions(struct mem_region *regions, in clear_map_dyn_mem_regions() argument
66 assert(regions != NULL); in clear_map_dyn_mem_regions()
71 begin = regions[i].base; in clear_map_dyn_mem_regions()
72 size = regions[i].nbytes; in clear_map_dyn_mem_regions()
|
| /arm-trusted-firmware-2.8.0/services/std_svc/drtm/ |
| A D | drtm_dma_prot.c | 249 drtm_mem_region_t regions[1]; in drtm_dma_prot_serialise_table() member
253 .num_regions = sizeof(((struct descr_table_1 *)NULL)->regions) / in drtm_dma_prot_serialise_table()
254 sizeof(((struct descr_table_1 *)NULL)->regions[0]) in drtm_dma_prot_serialise_table()
256 .regions = { in drtm_dma_prot_serialise_table()
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | xlat-tables-lib-v2-design.rst | 59 `mmap` regions
148 * The maximum number of `mmap` regions to map.
176 - number of `mmap` regions: ``MAX_MMAP_REGIONS``;
184 Static and dynamic memory regions
197 - *Dynamic regions* can be added or removed any time.
242 contrast with the dynamic regions APIs (for example
254 #. Add some static regions, add some dynamic regions.
260 regions can still be added or removed.
283 Dynamic regions are not allowed to overlap each other. Static regions are
331 From mmap regions to translation tables
[all …]
|
| A D | granule-protection-tables-design.rst | 51 small regions (granules) of memory can be assigned to different PAS with a 2
75 desired PAS regions is passed into the library which validates the mappings,
88 Defining PAS regions
149 are then added to the L1 PAS regions to be initialized in the next step and
184 * ``GPCCR_L0GPTSZ_30BITS`` (1GB regions, 0x40000000 bytes)
185 * ``GPCCR_L0GPTSZ_34BITS`` (16GB regions, 0x400000000 bytes)
186 * ``GPCCR_L0GPTSZ_36BITS`` (64GB regions, 0x1000000000 bytes)
187 * ``GPCCR_L0GPTSZ_39BITS`` (512GB regions, 0x8000000000 bytes)
|
| A D | secure-partition-manager-mm.rst | 58 - Memory and device regions in the system address map.
173 - ``plat_get_secure_partition_mmap()`` returns an array of mmap regions that
174 describe the memory regions that the SPM needs to allocate for a Secure
412 1. Device regions are mapped with nGnRE attributes and Execute Never
418 3. Read Only data memory regions are mapped with RO data and Execute Never
421 4. Read Write data memory regions are mapped with RW data and Execute Never
425 regions then all memory regions will be marked with Code memory region
607 The SPM is responsible for enabling access to regions of memory in the system
608 address map from a Secure Partition. This is done by mapping these regions in
630 of its memory regions. The SPM provides this feature through the
[all …]
|
| A D | ffa-manifest-binding.rst | 100 - value type: "memory-regions" node
101 - Specific "memory-regions" nodes that describe the RX/TX buffers expected
179 - Must be the string "arm,ffa-manifest-memory-regions".
216 - Must be the string "arm,ffa-manifest-device-regions".
|
| A D | secure-partition-manager.rst | 380 differ from 4KB, and to configure the regions allocated within the SP package,
564 The SP manifest may contain memory and device regions nodes. In case of
567 - Memory regions are mapped in the SP EL1&0 Stage-2 translation regime at
569 specify RX/TX buffer regions in which case it is not necessary for an SP
571 - Device regions are mapped in the SP EL1&0 Stage-2 translation regime (or
1056 Secure and non-secure IPA regions (rooted to by ``VTTBR_EL2`` and ``VSTTBR_EL2``)
1455 management transactions on their behalf. The acccess to the MMIO regions of
1509 for memory regions.
|
| A D | realm-management-extension.rst | 29 memory regions as Root or Realm respectively.
|
| /arm-trusted-firmware-2.8.0/plat/arm/board/fvp/fdts/ |
| A D | optee_sp_manifest.dts | 35 device-regions {
36 compatible = "arm,ffa-manifest-device-regions";
|
| /arm-trusted-firmware-2.8.0/include/lib/ |
| A D | utils.h | 37 void clear_map_dyn_mem_regions(struct mem_region *regions,
|
| /arm-trusted-firmware-2.8.0/plat/rpi/rpi4/ |
| A D | rpi4_bl31_setup.c | 216 int regions = fdt_num_mem_rsv(dtb); in remove_spintable_memreserve() local
219 for (i = 0; i < regions; i++) { in remove_spintable_memreserve()
|
| /arm-trusted-firmware-2.8.0/docs/threat_model/ |
| A D | threat_model_fvp_r.rst | 87 Arguably, MPUs having fewer memory regions, there may be a temptation to
88 share memory regions, making this a greater threat. However, since the
89 fvp_r implementation is limited to BL1, since BL1's regions are fixed,
|
| A D | threat_model.rst | 667 | | and sizes identifying memory regions, are |
821 | | regions. |
|
| A D | threat_model_el3_spm.rst | 599 | | regions to allow lender to proceed. |
|
| A D | threat_model_spm.rst | 360 | | statically alocated memory regions through the SMMU|
|
| /arm-trusted-firmware-2.8.0/docs/security_advisories/ |
| A D | security-advisory-tfv-3.rst | 47 permissions separately to data access permissions. All RO normal memory regions
66 - The xlat\_tables library ensures that all Read-Write (RW) memory regions are
|
| A D | security-advisory-tfv-1.rst | 154 regions mapped in by ARM platforms. Here, ``mem_size`` may be the
|
| /arm-trusted-firmware-2.8.0/fdts/ |
| A D | n1sdp-multi-chip.dts | 96 #redistributor-regions = <2>;
|
| /arm-trusted-firmware-2.8.0/docs/getting_started/ |
| A D | porting-guide.rst | 453 regions even when the MMU is enabled. If not defined, only static
463 image, ``MAX_XLAT_TABLES`` must be defined to accommodate the dynamic regions
468 Defines the maximum number of regions that are allocated by the translation
471 defined in the ``mmap_region_t`` structure. The platform defines the regions
475 required regions for each BL stage. If ``PLAT_XLAT_TABLES_DYNAMIC`` flag is
477 the dynamic regions as well.
855 which describes the regions of normal memory, memory mapped I/O
916 containing the maximum number of protected regions and bitmap with the types
928 This function returns the maximum size of DMA protected regions table in
|
| /arm-trusted-firmware-2.8.0/docs/ |
| A D | change-log.md | 3426 - Define memory regions for multi-chip platforms
3428 - Define default list of memory regions for DMC-620 TZC
3530 - Update OP-TEE SP manifest with device-regions node
3916 - The maximum number of memory map regions has been increased to 20
4259 - BL31: Split into two separate memory regions
4332 ddr regions, bring TZRAM_SIZE values in lined, and prevent macro expansion
4657 - Ignore empty regions in resource description
4877 - xlat_tables: Support mapping regions without an explicitly specified VA
5793 Version 2 of the translation table also added support for dynamic regions;
5795 Static regions can only be added or removed before the MMU is enabled.
[all …]
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | firmware-design.rst | 67 combination of the following types of memory regions. Each bootloader stage uses
68 one or more of these memory regions.
1606 memory regions to set the right memory attributes. When
2273 memory regions then it needs to map them using different memory pages.
|