Home
last modified time | relevance | path

Searched refs:AP (Results 1 – 16 of 16) sorted by relevance

/arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/misc/
A Dmvebu-a8k-addr-map.rst10 …|| AP DMA | | | | | +-------------+ …
11 …|| SD/eMMC | | CA72 CPUs | | AP MSS | +-------------+ …
14 …| | | | | +----- Translaton | |AP |…
19 …| | +-| translation | | Lookup +---- +--------- AP SPI |…
22 …| +------------| SMMU +---------+ | | Windows +--------- AP MCI0/1 |…
25 …| - | | +--------- AP STM |…
27 …| AP | | +-+---------+ …
A Dmvebu-ccu.rst13 specific AP.
A Dmvebu-io-win.rst24 specific AP.
/arm-trusted-firmware-2.8.0/docs/getting_started/
A Dimage-terminology.rst18 ambiguity (for example, within AP specific code/documentation), it is
52 AP Boot ROM: ``AP_BL1``
57 and authenticate an updateable AP firmware image into an executable RAM
60 AP RAM Firmware: ``AP_BL2``
85 AP Normal World Firmware: ``AP_BL33``
90 Other AP 3rd level images: ``AP_BL3_XXX``
124 make sense to interleave the image terminology for AP and SCP; both AP and SCP
136 AP-centric.
144 AP Firmware Update Boot ROM: ``AP_NS_BL1U``
157 AP Firmware Update Config: ``AP_BL2U``
[all …]
A Dporting-guide.rst247 Defines the maximum message size between AP and RSS. Need to define if
315 If the AP Firmware Updater Configuration image, BL2U is used, the following
2032 The AP Firmware Updater Configuration, BL2U, is an optional part of the FWU
2036 #. (Optional) Transferring the optional SCP_BL2U binary image from AP secure
2038 ``SCP_BL2U_BASE`` defines the address in AP secure memory where SCP_BL2U
2114 Application Processor (AP) for BL2U execution to continue.
/arm-trusted-firmware-2.8.0/docs/plat/arm/tc/
A Dindex.rst9 loaded by AP BL2 from FIP in flash to SRAM for copying by SCP (SCP has access
10 to AP SRAM).
28 The execution begins from SCP_BL1. SCP_BL1 powers up the AP which starts
30 FIP to SRAM. The SCP has access to AP SRAM. The address and size of SCP_BL2
32 RAM and starts executing it. The AP then continues executing the rest of TF-A
/arm-trusted-firmware-2.8.0/docs/plat/arm/morello/
A Dindex.rst16 execution. SCP_BL2 powers up the AP which starts execution at AP_BL31. The AP
/arm-trusted-firmware-2.8.0/include/plat/marvell/armada/a8k/common/
A Darmada_common.h55 AP enumerator
/arm-trusted-firmware-2.8.0/plat/marvell/armada/a8k/common/
A Dplat_ble_setup.c658 case(AP): in ble_skip_image_gpio()
/arm-trusted-firmware-2.8.0/docs/design/
A Dtrusted-board-boot-build.rst85 - NS_BL2U. The AP non-secure Firmware Updater image.
A Dfirmware-design.rst53 - Boot Loader stage 1 (BL1) *AP Trusted ROM*
61 - Boot Loader stage 1 (BL1) *AP Trusted ROM*
428 memory. The SCP executes SCP_BL2 and signals to the Application Processor (AP)
/arm-trusted-firmware-2.8.0/docs/plat/arm/
A Darm-build-options.rst131 compatible change to the MTL protocol, used for AP/SCP communication.
/arm-trusted-firmware-2.8.0/docs/perf/
A Dpsci-performance-juno.rst140 AP CPU to enter WFI before making the channel available to other CPUs, which
/arm-trusted-firmware-2.8.0/docs/components/
A Dfirmware-update.rst177 authentication). Secure world certificates and non-AP images are examples
/arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/
A Dbuild.rst127 Total amount of CPs (South Bridge) connected to AP. When the parameter is omitted,
/arm-trusted-firmware-2.8.0/docs/
A Dchange-log.md104 …- add MHU addresses for AP-RSS comms on TC2 ([6299c3a](https://review.trustedfirmware.org/plugins/…
105 …- add RSS-AP message size macro ([445130b](https://review.trustedfirmware.org/plugins/gitiles/TF-A…
848 …- rename AP-RSS message size macro ([70247dd](https://review.trustedfirmware.org/plugins/gitiles/T…
1637 …- change the AP runtime UART address ([07302a2](https://review.trustedfirmware.org/plugins/gitiles…
5352 - Add support for SCMI AP core configuration protocol v1.0
5353 - Use SCMI AP core protocol to set the warm boot entrypoint
5590 for communication between SCP and the AP CPU, replacing Boot-Over_MHU (BOM)

Completed in 29 milliseconds