Searched refs:structure (Results 1 – 25 of 33) sorted by relevance
12
| /trusted-firmware-a-latest/docs/plat/ |
| D | xilinx-versal.rst | 56 The PLM populates a data structure with image information for the TF-A. The TF-A
58 data structure is passed in the ```PMC_GLOBAL_GLOB_GEN_STORAGE4``` register.
|
| 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
|
| D | nvidia-tegra.rst | 68 Directory structure
116 structure via 'x1' register from the BL2 layer which is used by the
|
| /trusted-firmware-a-latest/docs/components/ |
| D | granule-protection-tables-design.rst | 6 to initialize the GPTs based on a data structure containing information about
53 when setting up the configuration structure.
74 the table creation step, a data structure containing information about the
79 structure used by the granule transition service which will be covered more
91 A ``pas_region_t`` structure is a way to represent a physical address space and
94 This structure is composed of the following:
110 and PAS type as arguments to generate the pas_region_t structure. As the names
|
| D | rmm-el3-comms-spec.rst | 194 field is also optional and platform can choose to zero out this structure if
201 For the data structure specification of Boot Manifest, refer to
533 RMM-EL3 Boot Manifest structure
536 The RMM-EL3 Boot Manifest v0.2 structure contains platform boot information passed
539 The members of the RMM-EL3 Boot Manifest structure are shown in the following
551 | plat_dram | 16 | ns_dram_info | NS DRAM Layout Info structure |
556 NS DRAM Layout Info structure
559 NS DRAM Layout Info structure contains information about platform Non-secure
560 DRAM layout. The members of this structure are shown in the table below:
577 NS DRAM Bank structure
[all …]
|
| D | xlat-tables-lib-v2-design.rst | 224 Although the ``mmap_region`` structure is a publicly visible type, it is not
228 compatibility breaks, should the ``mmap_region`` structure type evolve in the
271 successfully added before updating the translation context structure. If the
292 Code structure
|
| D | ras.rst | 184 macros create a structure of type ``struct err_record_info`` from its arguments,
259 For each RAS interrupt, the platform has to provide structure of type ``struct
|
| D | arm-sip-service.rst | 123 Format of the dir_t structure as such:
|
| /trusted-firmware-a-latest/docs/components/fconf/ |
| 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|.
|
| /trusted-firmware-a-latest/include/export/ |
| D | README | 22 - They must only contain macro, type and structure definitions, no prototypes.
|
| /trusted-firmware-a-latest/docs/design_documents/ |
| 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
199 This function measures the given critical data structure and records its
|
| D | cmake_framework.rst | 48 diagram provides an overview of the framework structure:
50 |Framework structure|
156 .. |Framework structure| image::
|
| D | rss.rst | 107 Message structure
309 structure is defined in
348 - First parameter is the pointer to the ``rss_mboot_metadata`` structure.
|
| /trusted-firmware-a-latest/docs/plat/st/ |
| D | stm32mpus.rst | 17 The TF-A image must be properly formatted with a STM32 header structure
|
| /trusted-firmware-a-latest/include/drivers/brcm/emmc/ |
| D | emmc_csl_sdprot.h | 389 uint32_t structure:2; member
|
| /trusted-firmware-a-latest/docs/components/spd/ |
| D | tlk-dispatcher.rst | 65 TLK expects the TZDRAM size and a structure containing the boot arguments. BL2
|
| /trusted-firmware-a-latest/docs/getting_started/ |
| D | psci-lib-integration-guide.rst | 80 ``cpu_context_t`` data structure. The initialization of other non-secure CPU
90 use the same ``cpu_context_t`` data structure for PSCI CPU context management
113 Currently the ``cpu_context_t`` data structure for AArch32 stores the following
183 structure and is declared in ``psci_lib.h`` header as follows:
378 This function must return the pointer to the ``cpu_context_t`` structure for
392 This function must return the pointer to the ``cpu_context_t`` structure for
|
| /trusted-firmware-a-latest/plat/nvidia/tegra/scat/ |
| D | bl31.scat | 136 * RELA data structure are aligned.
|
| /trusted-firmware-a-latest/docs/design/ |
| 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 …]
|
| 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
651 BL2, a platform that uses an extended entry_point_info structure to convey
662 uint8_t type; /* type of the structure */
663 uint8_t version; /* version of this structure */
664 uint16_t size; /* size of this structure in bytes */
733 evolution of TF-A using ``R0`` to pass a ``bl_params`` structure.
[all …]
|
| D | auth-framework.rst | 342 This ASN.1 structure makes it possible to remove any assumption about the
515 The AM defines the following structure to identify an authentication parameter
534 For each method, the AM defines a structure with the parameters required to
557 The AM defines the following structure to describe an authentication method for
586 The AM defines the following structure to store the data corresponding to an
603 The AM defines the following structure to enable an image to describe the
633 The following data structure describes an image in a CoT.
|
| D | psci-pd-tree.rst | 14 in a data structure.
|
| /trusted-firmware-a-latest/docs/ |
| 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
1227 By default, the platform will read the metadata structure and try to boot from
1541 #. Populating a ``meminfo`` structure with the following information in memory,
1549 By default, BL1 places this ``meminfo`` structure at the end of secure
1553 ``meminfo`` structure for BL2 or restrict the amount of memory visible to
1628 a ``meminfo`` structure containing the extents and availability of secure RAM for
[all …]
|
| /trusted-firmware-a-latest/docs/process/ |
| 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:
|
| /trusted-firmware-a-latest/drivers/brcm/emmc/ |
| D | emmc_csl_sdcmd.c | 169 card->csd.mmc.structure = (resp.data.r2.rsp4 >> 22) & 0x3; in sd_cmd9()
|
12
