Home
last modified time | relevance | path

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

/rk3399_ARM-atf/plat/nvidia/tegra/soc/t194/
H A 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()
/rk3399_ARM-atf/docs/components/
H A 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
137 handles these errors and returns back to TF-A Tests
151 Inject uncontainable RAS errors which causes platform to panic.
165 Inject and handle RAS errors in TF-A tests (no El3 involvement)
169 Reflection of synchronized errors from EL3 to TF-A tests, two tests one each for reflecting
184 Uncontainable Errors, Double Fault, and errors rising from EL3 execution. Please
190 RAS nodes are components in the system capable of signalling errors to PEs
[all …]
H A Drmm-el3-comms-spec.rst240 ``E_RMM_OK``,No errors detected,0
344 a failure. The errors are ordered by condition check.
352 ``E_RMM_OK``,No errors detected
387 a failure. The errors are ordered by condition check.
395 ``E_RMM_OK``,No errors detected
433 a failure. The errors are ordered by condition check.
443 ``E_RMM_OK``,No errors detected
507 a failure. The errors are ordered by condition check.
519 ``E_RMM_OK``,No errors detected
593 a failure. The errors are ordered by condition check.
[all …]
H A Dsdei.rst389 One of the examples is a memory region which continuously generates RAS errors.
/rk3399_ARM-atf/docs/process/
H A 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 …]
H A Dsecurity-hardening.rst11 Part of the security of a platform is handling errors correctly, as described in
H A Dcoding-style.rst173 adopted to follow MISRA guidelines more closely and to help prevent errors.
H A Dcontributing.rst276 At the bare minimum, TF-A code should build without any errors for every
/rk3399_ARM-atf/drivers/brcm/emmc/
H A 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()
/rk3399_ARM-atf/docs/threat_model/firmware_threat_model/
H A Dthreat_model_firmware_handoff.rst111 | | copy-related bugs (e.g., errors in ``memcpy`` or |
H A Dthreat_model.rst423 | | where memory corruption security errors can arise. |
425 | | | Some of the errors include integer overflow, |
430 | | errors in release builds. |
464 | | programming errors in debug builds. Other types of |
465 | | errors are handled through condition checks that |
/rk3399_ARM-atf/docs/plat/marvell/armada/
H A 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.
/rk3399_ARM-atf/docs/design/
H A Dfirmware-design.rst917 initialization if service declaration errors are detected. The framework does
1210 Before handling any lower EL exception, we synchronize the errors at EL3 entry to ensure
1211 that any errors pertaining to lower EL is isolated/identified. If we continue without
1212 identifying these errors early on then these errors will trigger in EL3 (as SError from
1216 To solve this problem, synchronize the errors at EL3 entry and check for any pending
1217 errors (async EA). If there is no pending error then continue with original exception.
H A Dinterrupt-framework-design.rst344 library APIs. The handler should treat all error conditions as critical errors
/rk3399_ARM-atf/docs/
H A Dchange-log.md984 …- report argument errors before bailing out ([ab5db33](https://review.trustedfirmware.org/plugins/…
4589 …- enable FHI PPI interrupt to report CPU errors ([f1e4a28](https://review.trustedfirmware.org/plug…
5484 …- fix build errors for latexpdf ([443d6ea](https://review.trustedfirmware.org/plugins/gitiles/TF-A…
5572 …- resolve build errors due to compiler optimization ([e8f0dd5](https://review.trustedfirmware.org/…
7074 …- resolve the static-checks errors ([066450a](https://review.trustedfirmware.org/plugins/gitiles/T…
10028 - Filter errors related to clock gate permissions
10151 - Fixed compilation errors with -O0 compile option
10484 - Fixed compilation errors for dual-root Chains of Trust caused by symbol
10487 - Fixed compilation errors on platforms with fewer than 4 cores caused by
10489 - Fixed compilation errors when building a position-independent image
[all …]
H A Dporting-guide.rst1371 Possible errors reported by the generic code are:
3789 RAS errors should be masked by writing any relevant error records in any
3837 Uncontainable errors, the intention of this function is to initiate orderly
/rk3399_ARM-atf/docs/getting_started/
H A Dbuild-options.rst245 - ``E``: Boolean option to make warnings into errors. Default is 1.
751 Interrupts, resulting from errors in NS world, will be always trapped in
1231 result in errors. Includes some compiler specific flags. No warnings are