Home
last modified time | relevance | path

Searched refs:handled (Results 1 – 19 of 19) sorted by relevance

/rk3399_ARM-atf/plat/common/aarch64/
H A Dplat_common.c99 int handled = ras_ea_handler(ea_reason, syndrome, cookie, handle, flags); in plat_default_ea_handler() local
100 if (handled != 0) in plat_default_ea_handler()
/rk3399_ARM-atf/docs/components/
H A Dras.rst30 EA’s and Error interrupts corresponding to NS nodes are handled first in firmware
41 errors in Non-secure world are routed to and handled in EL3. Said errors are Synchronous
59 EA's originating/attributed to NS world are handled first in NS and Kernel navigates
72 reflected back to lower EL (KFH) or handled in EL3 itself (FFH).
135 Couple of tests, one each for sync EA and async EA from lower EL which gets handled in El3.
147 Inject an unrecoverable RAS error, which gets handled in EL3.
318 handled when they occur, but only after the exceptions are unmasked again.
321 This means that all exceptions routed to EL3 are handled immediately. |TF-A|
H A Dexception-handling.rst29 FIQs and IRQs routed to EL3 are not required to be handled in EL3.
32 exceptions are targeted at and handled in EL3. For instance:
119 handled or delegated.
156 handled over to S-EL1.
367 being handled: for interrupts, this is implied when the interrupt is
404 #. The ``SMC`` is handled by the same dispatcher that handled the exception
481 handled, and Non-secure execution resumes after ``SMC`` instruction.
586 particular, when an interrupt is being handled by the PE (i.e., the interrupt is
612 exception descriptor and the programmed priority of interrupts handled by the
H A Dsecure-partition-manager-mm.rst387 The entry point for service requests that should be handled as Fast Calls is
518 Zero or a positive value indicates that the event was handled successfully.
523 or a runtime request was handled successfully.
H A Dffa-manifest-binding.rst157 - Specifies how secure interrupts are handled when the SP is in a waiting
H A Dfirmware-update.rst335 Once the SMC is handled, BL1 returns from exception to the normal world caller.
H A Del3-spmc.rst343 The Hypervisor or OS kernel can issue the FFA_SPM_ID_GET call handled by the
/rk3399_ARM-atf/docs/design/
H A Dinterrupt-framework-design.rst8 #. It should be possible to route interrupts meant to be handled by secure
17 #. It should be possible to route interrupts meant to be handled by
33 the exception level(s) it is handled in.
37 context. It is always handled in Secure-EL1.
41 current execution context. It is always handled in either Non-secure EL1
46 always handled in EL3.
134 is handled by non-secure software.
211 handled in Secure-EL1. They can be delivered to Secure-EL1 via EL3 but they
212 cannot be handled in EL3.
508 non-secure state. Any non-secure interrupts will be handled as described
[all …]
H A Dfirmware-design.rst417 BL31 entrypoint. The exception is handled by the SMC exception handler
938 indicate the service is not handled. This ``rt_svc_descs_indices[]`` array is
/rk3399_ARM-atf/plat/arm/board/fvp/fdts/
H A Dfvp_spmc_manifest.dts39 * Platform specific SiP SMC call handled at EL3. Used
/rk3399_ARM-atf/docs/design_documents/
H A Ddrtm_poc.rst51 triggered as a SMC by DCE-Preamble and handled by D-CRTM, which launches the
H A Dcmake_framework.rst69 conflict checking, these shall be handled by the configuration tool.
H A Drse.rst296 rest of the metadata is handled as follows when a measurement slot is extended
/rk3399_ARM-atf/docs/
H A Dindex.rst66 and process, how security disclosures are handled, and the guidelines for
H A Dporting-guide.rst3857 received at EL3 while one is already being handled. I.e., a call to
H A Dchange-log.md482 …- check that CPUs handled a pabandon ([461b62b](https://review.trustedfirmware.org/plugins/gitiles…
8200 …- modify how configuration type is handled ([ec4f28e](https://review.trustedfirmware.org/plugins/g…
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model.rst465 | | errors are handled through condition checks that |
619 | | properly sanitized and handled with caution. |
1029 | Threat | | **Improperly handled SMC calls can leak register |
/rk3399_ARM-atf/docs/process/
H A Dcoding-guidelines.rst289 error. This situation should be handled in one of the following ways:
/rk3399_ARM-atf/docs/getting_started/
H A Dbuild-options.rst685 handled at EL3, and a panic will result. The exception to this rule is when
744 Group 0 interrupts are assumed to be handled by Secure EL1.
1098 the FIQ are handled in monitor mode and non secure world is not allowed