Home
last modified time | relevance | path

Searched refs:area (Results 1 – 12 of 12) sorted by relevance

/rk3399_ARM-atf/include/drivers/brcm/
H A Dfru.h116 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
/rk3399_ARM-atf/docs/plat/arm/corstone1000/
H A Dindex.rst16 processor. BL2 verification relies on the signature area at the
17 beginning of the BL2 image. This area is needed by the SecureEnclave
/rk3399_ARM-atf/fdts/
H A Dstmm_template.dts39 * ARM CSS SoC Peripherals area.
/rk3399_ARM-atf/plat/nxp/soc-lx2160a/
H A Dsoc.def81 # (The above area i.e 0x18000000 - 0x1800dfff is available
/rk3399_ARM-atf/docs/components/
H A Dsecure-partition-manager-mm.rst204 through a shared memory region. The location of data in the shared memory area
205 is passed as a parameter to the ``MM_COMMUNICATE`` SMC. The shared memory area
210 memory area. The shared memory area is implemented as per the guidelines
H A Drmm-el3-comms-spec.rst125 communication requires the use of the shared area, it is expected that RMM needs
169 ``E_RMM_BOOT_INVALID_SHARED_BUFFER``,Invalid pointer to shared memory area,-5
1027 address,x1,[63:0],Address, "Physical address of the reserved memory area."
/rk3399_ARM-atf/docs/plat/
H A Drpi3.rst130 The area between **0x10000000** and **0x11000000** has to be manually protected
132 to add a memreserve region that reserves the previously mentioned area.
/rk3399_ARM-atf/docs/process/
H A Dcode-review-guidelines.rst14 community. People with more expertise in one area of the code base can
H A Dcontributing.rst120 help, as it shows who has been working the most recently on this area of
/rk3399_ARM-atf/docs/
H A Dporting-guide.rst2386 This function returns the size of the shared area between EL3 and RMM (or 0 on
2387 failure). A pointer to the shared area (or a NULL pointer on failure) is stored
2399 RMM image and stores it in the area specified by manifest.
3162 allocated in a special area if it cannot fit in the platform's global static
H A Dchange-log.md102 …- add pseudo CRB area ([d771d57](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-f…
121 …- add pseudo CRB area ([235d975](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-f…
148 …- add pseudo CRB area ([66579ca](https://review.trustedfirmware.org/plugins/gitiles/TF-A/trusted-f…
328 …- prepare DDR secure area encryption for STM32MP13 ([d06b375](https://review.trustedfirmware.org/p…
339 …- prepare DDR secure area encryption ([f2b9807](https://review.trustedfirmware.org/plugins/gitiles…
2756 …- remove mapping of BL2 DT area ([60d0758](https://review.trustedfirmware.org/plugins/gitiles/TF-A…
4478 …- check loaded NS image area ([ae4860b](https://review.trustedfirmware.org/plugins/gitiles/TF-A/tr…
4604 …- increase BL1 RW area for PSA_CRYPTO implementation ([ce18938](https://review.trustedfirmware.org…
5068 …- add Event Log area behind Trustzone Controller ([d836df7](https://review.trustedfirmware.org/plu…
5112 …- removing the signature area ([5856a91](https://review.trustedfirmware.org/plugins/gitiles/TF-A/t…
[all …]
/rk3399_ARM-atf/docs/design/
H A Dfirmware-design.rst147 address is platform dependent but it is usually located in a Trusted ROM area.
392 populates a platform-specific area of memory with the entrypoint/load-address
405 initialization is complete. Hence, BL2 populates a platform-specific area of