| /rk3399_ARM-atf/docs/components/ |
| H A D | rmm-el3-comms-spec.rst | 199 field is optional and platform can choose to zero out this structure if 209 For the data structure specification of Boot Manifest, refer to 650 …],Address,"PA where the request structure is stored for the opcode RMM_EL3_TOKEN_SIGN_PUSH_REQ_OP,… 1091 RMM-EL3 Boot Manifest structure 1094 The RMM-EL3 Boot Manifest v0.5 structure contains platform boot information passed 1097 The members of the RMM-EL3 Boot Manifest structure are shown in the following 1109 | plat_dram | 16 | memory_info | NS DRAM Layout Info structure | 1113 | plat_ncoh_region | 64 | memory_info | Device non-coherent ranges Info structure | 1115 | plat_coh_region | 88 | memory_info | Device coherent ranges Info structure | 1126 Memory Info structure [all …]
|
| H A D | context-management-library.rst | 26 In TF-A, the context is represented as a data structure used by the EL3 firmware 159 #. ``cpu_data_array.c`` : contains per_cpu_data structure instantiation. 162 structure members in assembly code. 176 #. ``cpu_data.h`` : contains the public interface to Per CPU data structure. 205 allocates memory for the CPU data structure. 212 This CPU data structure has a member element with an array of pointers to hold 233 the Secure, Non-Secure and Realm context structure addresses to ensure proper 240 structure. These cached copies are used to service trapped reads of the 254 The members of the context structure used by the EL3 firmware to preserve the 337 During this process, the per_cpu_data structure gets initialized with statically [all …]
|
| H A D | granule-protection-tables-design.rst | 6 to initialize the GPTs based on a data structure containing information about 77 the table creation step, a data structure containing information about the 83 structure used by the granule transition service which will be covered more 99 A ``pas_region_t`` structure is a way to represent a physical address space and 102 This structure is composed of the following: 118 and PAS type as arguments to generate the pas_region_t structure. As the names 157 structure. Setting this option to 0 chooses a single spinlock for all GPT L1 268 structure (8) to get the size of array in bytes.
|
| H A D | ven-el3-debugfs.rst | 33 Format of the dir_t structure as such:
|
| H A D | xlat-tables-lib-v2-design.rst | 208 Although the ``mmap_region`` structure is a publicly visible type, it is not 212 compatibility breaks, should the ``mmap_region`` structure type evolve in the 254 successfully added before updating the translation context structure. If the 275 Code structure
|
| H A D | ras.rst | 213 macros create a structure of type ``struct err_record_info`` from its arguments, 288 For each RAS interrupt, the platform has to provide structure of type ``struct
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | index.rst | 42 structure. 84 anything appropriate: structure, array, function, etc.. 104 can be used to fill the C data structure with the data from the config |DTB|.
|
| H A D | tb_fw_bindings.rst | 138 If a structure includes a Chain of Trust (CoT) for secure authentication and 145 key integration. For full details on required properties and node structure,
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | cmake_framework.rst | 44 diagram provides an overview of the framework structure: 46 |Framework structure| 152 .. |Framework structure| image::
|
| H A D | measured_boot.rst | 88 TCG has specified the architecture for the structure of this log in the 90 log event records—the legacy, fixed size SHA1 structure called TCG_PCR_EVENT 91 and the variable length crypto agile structure called TCG_PCR_EVENT2. Event 208 This function measures the given critical data structure and records its
|
| /rk3399_ARM-atf/include/export/ |
| H A D | README | 22 - They must only contain macro, type and structure definitions, no prototypes.
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | xilinx-versal.rst | 115 The PLM populates a data structure with image information for the TF-A. The TF-A 117 data structure is passed in the ```PMC_GLOBAL_GLOB_GEN_STORAGE4``` register.
|
| H A D | xilinx-zynqmp.rst | 105 The FSBL populates a data structure with image information for TF-A. TF-A uses 107 structure is passed in the ``PMU_GLOBAL.GLOBAL_GEN_STORAGE6`` register. The
|
| H A D | nvidia-tegra.rst | 68 Directory structure 119 structure via 'x1' register from the BL2 layer which is used by the
|
| /rk3399_ARM-atf/docs/plat/st/ |
| H A D | stm32mpus.rst | 17 The TF-A image must be properly formatted with a STM32 header structure
|
| /rk3399_ARM-atf/include/drivers/brcm/emmc/ |
| H A D | emmc_csl_sdprot.h | 389 uint32_t structure:2; member
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A D | tlk-dispatcher.rst | 65 TLK expects the TZDRAM size and a structure containing the boot arguments. BL2
|
| /rk3399_ARM-atf/ |
| H A D | .versionrc.cjs | 34 * structure into one accepted by the Conventional Changelog adapter (conventional-changelog-tf-a).
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | firmware-design.rst | 115 - BL1 passes the address of a meminfo_t structure to BL2 via ``arg1``. This 116 structure contains the memory layout available to BL2. 282 contains an ``entry_point_info_t`` structure, which BL1 uses to initialize the 622 pass a ``bl31_params`` structure. 634 TF-A's BL2 implementation passes a ``bl31_params`` structure in 652 There are two variants of this structure, for AArch64: 680 BL2, a platform that uses an extended entry_point_info structure to convey 691 uint8_t type; /* type of the structure */ 692 uint8_t version; /* version of this structure */ 693 uint16_t size; /* size of this structure in bytes */ [all …]
|
| H A D | interrupt-framework-design.rst | 229 associated with each type of interrupt in the following data structure. 333 The ``handle`` parameter points to the ``cpu_context`` structure of the current CPU 338 ``cpu_context`` structure of the current CPU for the target security state. On 343 the structure pointed to by the returned pointer and via the context management 372 each security state in the ``cpu_context`` structure of each CPU. It exports the 636 data structure referenced by the ``SP_EL3``\ register. 639 per-cpu ``cpu_context`` data structure referenced by the ``SP_EL3`` register. 642 from the per-cpu ``cpu_context`` data structure in ``SP_EL0`` and 664 type. The ``handler`` is retrieved from the ``intr_type_desc_t`` structure as 672 structure for the current security state are passed to the handler function [all …]
|
| H A D | auth-framework.rst | 373 This ASN.1 structure makes it possible to remove any assumption about the 547 The AM defines the following structure to identify an authentication parameter 566 For each method, the AM defines a structure with the parameters required to 589 The AM defines the following structure to describe an authentication method for 618 The AM defines the following structure to store the data corresponding to an 635 The AM defines the following structure to enable an image to describe the 665 The following data structure describes an image in a CoT.
|
| /rk3399_ARM-atf/plat/nvidia/tegra/scat/ |
| H A D | bl31.scat | 136 * RELA data structure are aligned.
|
| /rk3399_ARM-atf/docs/ |
| H A D | porting-guide.rst | 478 defined in the ``mmap_region_t`` structure. The platform defines the regions 527 structure for use by the platform layer. 796 structure: 965 This function returns the address of plat_drtm_dma_prot_features_t structure 989 This function returns the address of *plat_drtm_tpm_features_t* structure 1248 By default, the platform will read the metadata structure and try to boot from 1548 This optional structure holds platform hooks for alternative images load. 1634 #. Populating a ``meminfo`` structure with the following information in memory, 1642 By default, BL1 places this ``meminfo`` structure at the end of secure 1646 ``meminfo`` structure for BL2 or restrict the amount of memory visible to [all …]
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | code-review-guidelines.rst | 129 - The structure of the code is clear. 187 - The general structure of the patch looks good. This covers things like:
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-options.rst | 976 - blocks) covered by a single bit of the bitlock structure during RME GPT 979 - for the bitlock structure. This numeric parameter can take the values 983 - structure. 1187 configuration device tree, instead of static structure in the code base. 1205 device tree in runtime rather than depending on static C structure at compile 1602 in defining the firmware update metadata structure. This flag is by default 1608 This flag is used in defining the firmware update metadata structure. This 1615 structure where a platform can choose to not include the firmware 1616 store description in the metadata structure. This option indicates 1618 the updatable images is part of the structure.
|