Searched refs:vector (Results 1 – 18 of 18) sorted by relevance
| /rk3399_ARM-atf/plat/allwinner/common/ |
| H A D | sunxi_scpi_pm.c | 215 uint32_t vector = SUNXI_SRAM_A2_BASE + OR1K_VEC_ADDR(i); in sunxi_set_scpi_psci_ops() local 216 uint32_t offset = SUNXI_SCP_BASE - vector; in sunxi_set_scpi_psci_ops() 218 mmio_write_32(vector, offset >> 2); in sunxi_set_scpi_psci_ops()
|
| H A D | arisc_off.S | 17 # start address in the reset vector), to be actually triggered by that
|
| /rk3399_ARM-atf/drivers/nxp/scmi/vendor/ |
| H A D | scmi_imx9.h | 153 uint64_t *vector);
|
| H A D | scmi_imx9.c | 333 uint32_t *sleepmode, uint64_t *vector) in scmi_core_info_get() argument 357 *vector = lo_addr | (uint64_t)hi_addr << 32; in scmi_core_info_get()
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | reset-design.rst | 40 If the reset vector address (reflected in the reset vector base address register 51 On both the FVP and Juno platforms, the reset vector address is not programmable 105 reset vector base address, before the application processor is powered on.
|
| H A D | interrupt-framework-design.rst | 447 initialisation. The TSP provides the address of the vector table 502 exception vector table. This is defined as the **asynchronous mode** of 600 The TSP also replaces the default exception vector table referenced through the 601 ``early_exceptions`` variable, with a vector table capable of handling FIQ and IRQ 631 When an interrupt is generated, the vector for each interrupt type is 646 at the FIQ vector. Non-secure interrupts will be signaled at the IRQ 647 vector. The platform should implement the following API to determine the 853 trigger at Secure-EL1 IRQ exception vector. The TSP saves the general purpose 924 vector table when ``PSTATE.I`` and ``PSTATE.F`` bits are 0. As described earlier, 1005 exception vector handles the non-secure interrupt and returns. The return value
|
| H A D | firmware-design.rst | 146 This stage begins execution from the platform's reset vector at EL3. The reset 151 vector defined by the constant ``BL1_RO_BASE``. The BL1 data section is copied 1176 location in memory where the handler is stored is called the exception vector. 1178 vector table. 1180 Each EL (except EL0) has its own vector table, VBAR_ELn register stores the base 1181 of vector table. Refer to `AArch64 exception vector table`_ 2932 .. _AArch64 exception vector table: https://developer.arm.com/documentation/100933/0100/AArch64-exc…
|
| H A D | auth-framework.rst | 264 /* Initialization vector. */
|
| /rk3399_ARM-atf/docs/plat/arm/automotive_rd/ |
| H A D | rdaspen.rst | 23 The SCP-firmware then sets the reset vector base address (RVBAR) for the AP, ensuring
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-aemv8-base.rst | 104 reset vector for each core.
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | security-hardening.rst | 34 vector.
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | warp7.rst | 7 the reset vector to the command-line in user-space.
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | context-management-library.rst | 13 The general-purpose registers, most of the system registers and vector registers 39 (EL2/EL1, vector, general-purpose registers), will be overwritten, as the software
|
| H A D | secure-partition-manager-mm.rst | 259 and installs a simple exception vector table in S-EL1 that relays a SVC request
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-options.rst | 63 vector instead of the BL1 entrypoint. It can take the value 0 (CPU reset to BL1 928 vector address can be programmed or is fixed on the platform. It can take 961 - ``RESET_TO_BL31``: Enable BL31 entrypoint as the CPU reset vector instead 967 in TF-A. This flag configures SP_MIN entrypoint as the CPU reset vector 1102 - ``SVE_VECTOR_LEN``: SVE vector length to configure in ZCR_EL3. 1363 vector into TF-A by potentially allowing an attacker to inject arbitrary data.
|
| /rk3399_ARM-atf/docs/ |
| H A D | porting-guide.rst | 685 BL1 by default implements the reset vector where execution starts from a cold 686 or warm boot. BL31 can be optionally set as a reset vector using the 689 For each CPU, the reset vector code is responsible for the following tasks: 702 reset vector code to perform the above tasks. 1620 BL1 implements the reset vector where execution starts from after a cold or 2184 If BL31 is a reset vector, It also needs to handle the reset as specified in
|
| H A D | change-log.md | 2010 …- set correct SVE vector lengths ([842ba2f](https://review.trustedfirmware.org/plugins/gitiles/TF-… 4893 …- modify vector entry paths ([d04c04a](https://review.trustedfirmware.org/plugins/gitiles/TF-A/tru… 6566 …- support full SVE vector length ([bebcf27](https://review.trustedfirmware.org/plugins/gitiles/TF-… 12149 - Added Call Frame Information (CFI) assembler directives to the vector entries
|
| /rk3399_ARM-atf/docs/threat_model/ |
| H A D | supply_chain_threat_model.rst | 328 | | end in some form of attack vector |
|