Searched refs:area (Results 1 – 12 of 12) sorted by relevance
| /trusted-firmware-a-3.4.0/include/drivers/brcm/ |
| D | fru.h | 116 int fru_parse_ddr(uint8_t *data, struct fru_area_info *area,
118 int fru_parse_board(uint8_t *data, struct fru_area_info *area,
127 static inline int fru_parse_ddr(uint8_t *data, struct fru_area_info *area, in fru_parse_ddr() argument
133 static inline int fru_parse_board(uint8_t *data, struct fru_area_info *area, in fru_parse_board() argument
|
| /trusted-firmware-a-3.4.0/docs/plat/arm/corstone1000/ |
| D | index.rst | 16 processor. BL2 verification relies on the signature area at the
17 beginning of the BL2 image. This area is needed by the SecureEnclave
|
| /trusted-firmware-a-3.4.0/services/std_svc/rmmd/trp/ |
| D | linker.lds | 58 * Define a linker symbol to mark the end of the RW memory area for this
|
| /trusted-firmware-a-3.4.0/plat/nxp/soc-lx2160a/ |
| D | soc.def | 81 # (The above area i.e 0x18000000 - 0x1800dfff is available
|
| /trusted-firmware-a-3.4.0/docs/components/ |
| D | rmm-el3-comms-spec.rst | 124 communication requires the use of the shared area, it is expected that RMM needs
164 ``E_RMM_BOOT_INVALID_SHARED_BUFFER``,Invalid pointer to shared memory area,-5
|
| D | secure-partition-manager-mm.rst | 211 through a shared memory region. The location of data in the shared memory area
212 is passed as a parameter to the ``MM_COMMUNICATE`` SMC. The shared memory area
217 memory area. The shared memory area is implemented as per the guidelines
|
| /trusted-firmware-a-3.4.0/docs/process/ |
| D | code-review-guidelines.rst | 19 community. People with more expertise in one area of the code base can
|
| D | contributing.rst | 108 help, as it shows who has been working the most recently on this area of
|
| /trusted-firmware-a-3.4.0/docs/plat/ |
| D | rpi3.rst | 130 The area between **0x10000000** and **0x11000000** has to be manually protected
132 to add a memreserve region that reserves the previously mentioned area.
|
| /trusted-firmware-a-3.4.0/docs/getting_started/ |
| D | porting-guide.rst | 2082 This function returns the size of the shared area between EL3 and RMM (or 0 on
2083 failure). A pointer to the shared area (or a NULL pointer on failure) is stored
2095 RMM image and stores it in the area specified by manifest.
2542 allocated in a special area if it cannot fit in the platform's global static
|
| /trusted-firmware-a-3.4.0/docs/design/ |
| D | firmware-design.rst | 142 address is platform dependent but it is usually located in a Trusted ROM area.
444 populates a platform-specific area of memory with the entrypoint/load-address
457 initialization is complete. Hence, BL2 populates a platform-specific area of
|
| /trusted-firmware-a-3.4.0/docs/ |
| D | change-log.md | 3802 - ti/k3: common: Fix RO data area size calculation
5094 address offset, and overlap completely but must not cover the same area.
5574 DRAM area so it is not a good example to use it.
|
