Home
last modified time | relevance | path

Searched refs:errors (Results 1 – 15 of 15) sorted by relevance

/trusted-firmware-a-latest/plat/nvidia/tegra/soc/t194/
Dplat_ras.c268 const struct ras_error *errors, uint64_t status) in tegra194_ras_node_handler() argument
294 for (uint32_t i = 0; errors[i].error_msg != NULL; i++) { in tegra194_ras_node_handler()
295 if (ierr == errors[i].error_code) { in tegra194_ras_node_handler()
297 errors[i].error_msg, ierr); in tegra194_ras_node_handler()
361 const struct ras_error *errors; in tegra194_ras_record_handler() local
373 errors = aux_data[offset].error_records; in tegra194_ras_record_handler()
376 assert(errors != NULL); in tegra194_ras_record_handler()
385 errors, status); in tegra194_ras_record_handler()
/trusted-firmware-a-latest/docs/components/
Dras.rst16 There are two philosophies for handling RAS errors from Non-secure world point
41 errors in Non-secure world are routed to and handled in EL3. Said errors are Synchronous
63 - KFH mode does not need any EL3 involvement except for the reflection of errors back
65 signaled to PE while executing at lower EL. During entry into EL3 the errors (EA) are
108 handles these errors and returns back to TF-A Tests
122 Inject uncontainable RAS errors which causes platform to panic.
136 Inject and handle RAS errors in TF-A tests (no El3 involvement)
140 Reflection of synchronized errors from EL3 to TF-A tests, two tests one each for reflecting
155 Uncontainable Errors, Double Fault, and errors rising from EL3 execution. Please
161 RAS nodes are components in the system capable of signalling errors to PEs
[all …]
Drmm-el3-comms-spec.rst232 ``E_RMM_OK``,No errors detected,0
327 a failure. The errors are ordered by condition check.
335 ``E_RMM_OK``,No errors detected
370 a failure. The errors are ordered by condition check.
378 ``E_RMM_OK``,No errors detected
416 a failure. The errors are ordered by condition check.
426 ``E_RMM_OK``,No errors detected
475 a failure. The errors are ordered by condition check.
485 ``E_RMM_OK``,No errors detected
Dsdei.rst389 One of the examples is a memory region which continuously generates RAS errors.
/trusted-firmware-a-latest/docs/process/
Dcoding-guidelines.rst33 Checkpatch errors will gate upstream merging of pull requests.
189 Using CASSERT to check for compile time data errors
221 Using assert() to check for programming errors
228 interpreting invalid state or bad function arguments as programming errors using
246 Handling integration errors
264 Handling recoverable errors
285 Handling unrecoverable errors
302 ``plat_error_handler`` may take additional action for some errors (for example,
307 Examples of unexpected unrecoverable errors:
319 Examples of expected unrecoverable errors:
[all …]
Dsecurity-hardening.rst11 Part of the security of a platform is handling errors correctly, as described in
Dcoding-style.rst170 adopted to follow MISRA guidelines more closely and to help prevent errors.
/trusted-firmware-a-latest/drivers/brcm/emmc/
Demmc_csl_sdcard.c53 static int err_recovery(struct sd_handle *handle, uint32_t errors);
816 static int err_recovery(struct sd_handle *handle, uint32_t errors) in err_recovery() argument
826 if (errors & SD_CMD_ERROR_INT) in err_recovery()
830 if (errors & SD_DAT_ERROR_INT) in err_recovery()
/trusted-firmware-a-latest/docs/threat_model/
Dthreat_model.rst420 | | where memory corruption security errors can arise. |
422 | | | Some of the errors include integer overflow, |
427 | | errors in release builds. |
461 | | programming errors in debug builds. Other types of |
462 | | errors are handled through condition checks that |
/trusted-firmware-a-latest/docs/plat/marvell/armada/
Dbuild.rst170 … When ``HANDLE_EA_EL3_FIRST_NS=1``, External Aborts and SError Interrupts, resulting from errors
186 to running Linux kernel and makes correctable errors as fatal aborts.
/trusted-firmware-a-latest/docs/
Dchange-log.md239 …- enable FHI PPI interrupt to report CPU errors ([f1e4a28](https://review.trustedfirmware.org/plug…
1134 …- fix build errors for latexpdf ([443d6ea](https://review.trustedfirmware.org/plugins/gitiles/TF-A…
1222 …- resolve build errors due to compiler optimization ([e8f0dd5](https://review.trustedfirmware.org/…
2724 …- resolve the static-checks errors ([066450a](https://review.trustedfirmware.org/plugins/gitiles/T…
5677 - Filter errors related to clock gate permissions
5800 - Fixed compilation errors with -O0 compile option
6133 - Fixed compilation errors for dual-root Chains of Trust caused by symbol
6136 - Fixed compilation errors on platforms with fewer than 4 cores caused by
6138 - Fixed compilation errors when building a position-independent image
6141 - Fixed compilation errors on Windows caused by a non-portable architecture
[all …]
Dporting-guide.rst1350 Possible errors reported by the generic code are:
3326 Uncontainable errors, the intention of this function is to initiate orderly
/trusted-firmware-a-latest/docs/design/
Dfirmware-design.rst885 initialization if service declaration errors are detected. The framework does
1165 Before handling any lower EL exception, we synchronize the errors at EL3 entry to ensure
1166 that any errors pertaining to lower EL is isolated/identified. If we continue without
1167 identifying these errors early on then these errors will trigger in EL3 (as SError from
1171 To solve this problem, synchronize the errors at EL3 entry and check for any pending
1172 errors (async EA). If there is no pending error then continue with original exception.
Dinterrupt-framework-design.rst344 library APIs. The handler should treat all error conditions as critical errors
/trusted-firmware-a-latest/docs/getting_started/
Dbuild-options.rst226 - ``E``: Boolean option to make warnings into errors. Default is 1.
578 Interrupts, resulting from errors in NS world, will be always trapped in
984 result in errors. Includes some compiler specific flags. No warnings are