Home
last modified time | relevance | path

Searched refs:reason (Results 1 – 25 of 30) sorted by relevance

12

/trusted-firmware-a-3.6.0-3.5.0/lib/semihosting/
Dsemihosting.c225 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()
/trusted-firmware-a-3.6.0-3.5.0/include/lib/
Dsemihosting.h58 void semihosting_exit(uint32_t reason, uint32_t subcode);
/trusted-firmware-a-3.6.0-3.5.0/plat/renesas/rzg/
Dbl2_plat_setup.c315 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()
/trusted-firmware-a-3.6.0-3.5.0/plat/renesas/rcar/
Dbl2_plat_setup.c333 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()
/trusted-firmware-a-3.6.0-3.5.0/docs/plat/
Drcar-gen3.rst75 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:
Drz-g2.rst74 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
Dimx8m.rst96 The reason for the MT_RW attribute mapping scheme is the fact that the SMC
Dsocionext-uniphier.rst60 BL2 must be compressed for the reason above. The UniPhier's platform makefile
Drpi3.rst295 - ``EL3_PAYLOAD_BASE``: The reason is that you can already load anything to any
/trusted-firmware-a-3.6.0-3.5.0/
D.editorconfig43 # reason for changes.
/trusted-firmware-a-3.6.0-3.5.0/plat/imx/common/include/sci/svc/pm/
Dsci_pm_api.h583 sc_err_t sc_pm_reset_reason(sc_ipc_t ipc, sc_pm_reset_reason_t *reason);
/trusted-firmware-a-3.6.0-3.5.0/plat/imx/common/sci/svc/pm/
Dpm_rpc_clnt.c360 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()
/trusted-firmware-a-3.6.0-3.5.0/plat/xilinx/common/include/
Dpm_api_sys.h32 enum pm_ret_status pm_abort_suspend(enum pm_abort_reason reason, uint32_t flag);
/trusted-firmware-a-3.6.0-3.5.0/plat/xilinx/common/pm_service/
Dpm_api_sys.c173 enum pm_ret_status pm_abort_suspend(enum pm_abort_reason reason, uint32_t flag) in pm_abort_suspend() argument
185 reason, primary_proc->node_id); in pm_abort_suspend()
/trusted-firmware-a-3.6.0-3.5.0/plat/xilinx/zynqmp/pm_service/
Dzynqmp_pm_api_sys.h86 enum pm_ret_status pm_abort_suspend(enum pm_abort_reason reason);
Dzynqmp_pm_api_sys.c386 enum pm_ret_status pm_abort_suspend(enum pm_abort_reason reason) in pm_abort_suspend() argument
397 PM_PACK_PAYLOAD3(payload, PM_ABORT_SUSPEND, reason, in pm_abort_suspend()
/trusted-firmware-a-3.6.0-3.5.0/fdts/
Dstm32mp151a-prtt1a.dts190 * reason, so it should do no harm. All inputs configured with
/trusted-firmware-a-3.6.0-3.5.0/docs/security_advisories/
Dsecurity-advisory-tfv-8.rst67 For this reason, TF-A does not save ``x0`` to ``x3`` in the CPU context on an
/trusted-firmware-a-3.6.0-3.5.0/docs/components/
Dxlat-tables-lib-v2-design.rst239 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
Dras.rst157 including the reason for the error, exception syndrome, and also ``flags``,
Drmm-el3-comms-spec.rst152 be returned in x1 and it will encode a signed integer with the error reason
/trusted-firmware-a-3.6.0-3.5.0/docs/process/
Dcoding-style.rst188 The reason for this is to prevent accidental changes to control flow when
Dcoding-guidelines.rst499 reason, the TF-A project used to make heavy use of weak functions and there
/trusted-firmware-a-3.6.0-3.5.0/docs/plat/marvell/armada/
Dbuild.rst101 There is no reason to enable this feature if OP-TEE OS built with CFG_WITH_PAGER=n.
/trusted-firmware-a-3.6.0-3.5.0/docs/design_documents/
Dmeasured_boot_poc.rst41 The reason to choose OP-TEE Toolkit to build our PoC around it is mostly

12