| /arm-trusted-firmware-2.8.0/lib/semihosting/ |
| A D | semihosting.c | 225 void semihosting_exit(uint32_t reason, uint32_t subcode) in semihosting_exit() argument
228 uint64_t parameters[] = {reason, subcode}; in semihosting_exit()
233 (void)semihosting_call(SEMIHOSTING_SYS_EXIT, reason); in semihosting_exit()
|
| /arm-trusted-firmware-2.8.0/include/lib/ |
| A D | semihosting.h | 58 void semihosting_exit(uint32_t reason, uint32_t subcode);
|
| /arm-trusted-firmware-2.8.0/plat/renesas/rzg/ |
| A D | bl2_plat_setup.c | 315 static uint32_t reason = RCAR_COLD_BOOT; in is_ddr_backup_mode() local
319 return reason; in is_ddr_backup_mode()
324 return reason; in is_ddr_backup_mode()
327 reason = RCAR_WARM_BOOT; in is_ddr_backup_mode()
328 return reason; in is_ddr_backup_mode()
|
| /arm-trusted-firmware-2.8.0/plat/renesas/rcar/ |
| A D | bl2_plat_setup.c | 333 static uint32_t reason = RCAR_COLD_BOOT; in is_ddr_backup_mode() local
340 return reason; in is_ddr_backup_mode()
344 return reason; in is_ddr_backup_mode()
353 reason = RCAR_WARM_BOOT; in is_ddr_backup_mode()
355 reason = RCAR_WARM_BOOT; in is_ddr_backup_mode()
357 return reason; in is_ddr_backup_mode()
|
| /arm-trusted-firmware-2.8.0/docs/plat/ |
| A D | rcar-gen3.rst | 75 PMIC) before determining the boot reason (cold or warm).
81 Once BL2 boots, it determines the boot reason, writes it to shared
86 it still needs to initialize the rest of the cores; this is the reason
92 Depending on the boot reason BL31 initializes the rest of the cores:
|
| A D | rz-g2.rst | 74 BL2 initializes DDR before determining the boot reason (cold or warm).
76 Once BL2 boots, it determines the boot reason, writes it to shared
81 it still needs to initialize the rest of the cores; this is the reason
|
| A D | imx8m.rst | 96 The reason for the MT_RW attribute mapping scheme is the fact that the SMC
|
| A D | socionext-uniphier.rst | 60 BL2 must be compressed for the reason above. The UniPhier's platform makefile
|
| A D | rpi3.rst | 295 - ``EL3_PAYLOAD_BASE``: The reason is that you can already load anything to any
|
| /arm-trusted-firmware-2.8.0/plat/xilinx/versal/pm_service/ |
| A D | pm_api_sys.c | 116 enum pm_ret_status pm_abort_suspend(enum pm_abort_reason reason, uint32_t flag) in pm_abort_suspend() argument
128 reason, primary_proc->node_id); in pm_abort_suspend()
|
| A D | pm_api_sys.h | 32 enum pm_ret_status pm_abort_suspend(enum pm_abort_reason reason, uint32_t flag);
|
| /arm-trusted-firmware-2.8.0/ |
| A D | .editorconfig | 43 # reason for changes.
|
| /arm-trusted-firmware-2.8.0/plat/imx/common/include/sci/svc/pm/ |
| A D | sci_pm_api.h | 583 sc_err_t sc_pm_reset_reason(sc_ipc_t ipc, sc_pm_reset_reason_t *reason);
|
| /arm-trusted-firmware-2.8.0/plat/imx/common/sci/svc/pm/ |
| A D | pm_rpc_clnt.c | 360 sc_err_t sc_pm_reset_reason(sc_ipc_t ipc, sc_pm_reset_reason_t *reason) in sc_pm_reset_reason() argument
373 if (reason != NULL) { in sc_pm_reset_reason()
374 *reason = RPC_U8(&msg, 0U); in sc_pm_reset_reason()
|
| /arm-trusted-firmware-2.8.0/plat/xilinx/zynqmp/pm_service/ |
| A D | pm_api_sys.h | 84 enum pm_ret_status pm_abort_suspend(enum pm_abort_reason reason);
|
| A D | pm_api_sys.c | 389 enum pm_ret_status pm_abort_suspend(enum pm_abort_reason reason) in pm_abort_suspend() argument
400 PM_PACK_PAYLOAD3(payload, PM_ABORT_SUSPEND, reason, in pm_abort_suspend()
|
| /arm-trusted-firmware-2.8.0/docs/security_advisories/ |
| A D | security-advisory-tfv-8.rst | 67 For this reason, TF-A does not save ``x0`` to ``x3`` in the CPU context on an
|
| /arm-trusted-firmware-2.8.0/docs/components/ |
| A D | xlat-tables-lib-v2-design.rst | 239 static regions. For this reason (and to retain backward compatibility with the
369 The most common reason for needing a sub-table is when a specific mapping
372 memory than expected. The reason is that all levels of translation are
|
| A D | ras.rst | 113 including the reason for the error, exception syndrome, and also ``flags``,
|
| A D | rmm-el3-comms-spec.rst | 152 be returned in x1 and it will encode a signed integer with the error reason
|
| /arm-trusted-firmware-2.8.0/docs/process/ |
| A D | coding-style.rst | 188 The reason for this is to prevent accidental changes to control flow when
|
| /arm-trusted-firmware-2.8.0/docs/plat/marvell/armada/ |
| A D | build.rst | 101 There is no reason to enable this feature if OP-TEE OS built with CFG_WITH_PAGER=n.
|
| /arm-trusted-firmware-2.8.0/docs/design_documents/ |
| A D | measured_boot_poc.rst | 41 The reason to choose OP-TEE Toolkit to build our PoC around it is mostly
|
| /arm-trusted-firmware-2.8.0/docs/plat/arm/fvp/ |
| A D | index.rst | 523 Payload. For the same reason, the FDT needs to be compiled from the DT source
|
| /arm-trusted-firmware-2.8.0/docs/design/ |
| A D | interrupt-framework-design.rst | 138 reason to route the interrupt to EL3 software and then hand it back to
|