| /trusted-firmware-a/plat/nvidia/tegra/soc/t194/ |
| A D | plat_ras.c | 275 const struct ras_error *errors, uint64_t status) in tegra194_ras_node_handler() argument
301 for (uint32_t i = 0; errors[i].error_msg != NULL; i++) { in tegra194_ras_node_handler()
302 if (ierr == errors[i].error_code) { in tegra194_ras_node_handler()
304 errors[i].error_msg, ierr); in tegra194_ras_node_handler()
368 const struct ras_error *errors; in tegra194_ras_record_handler() local
380 errors = aux_data[offset].error_records; in tegra194_ras_record_handler()
383 assert(errors != NULL); in tegra194_ras_record_handler()
392 errors, status); in tegra194_ras_record_handler()
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/components/ |
| A D | ras.rst.txt | 9 paradigm for handling platform errors: exceptions resulting from errors are
10 routed to and handled in EL3. Said errors are Synchronous External Abort (SEA),
24 exceptions resulting from platform errors in EL3. It allows the platform to
46 Uncontainable Errors, Double Fault, and errors rising from EL3 execution. Please
52 RAS nodes are components in the system capable of signalling errors to PEs
62 - A handler to probe error records for errors;
145 RAS nodes can signal errors to the PE by raising Fault Handling and/or Error
|
| /trusted-firmware-a/docs/components/ |
| A D | ras.rst | 9 paradigm for handling platform errors: exceptions resulting from errors are
10 routed to and handled in EL3. Said errors are Synchronous External Abort (SEA),
24 exceptions resulting from platform errors in EL3. It allows the platform to
46 Uncontainable Errors, Double Fault, and errors rising from EL3 execution. Please
52 RAS nodes are components in the system capable of signalling errors to PEs
62 - A handler to probe error records for errors;
145 RAS nodes can signal errors to the PE by raising Fault Handling and/or Error
|
| /trusted-firmware-a/docs/process/ |
| A D | coding-guidelines.rst | 33 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 …]
|
| A D | security-hardening.rst | 11 Part of the security of a platform is handling errors correctly, as described in
|
| A D | coding-style.rst | 170 adopted to follow MISRA guidelines more closely and to help prevent errors.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/process/ |
| A D | coding-guidelines.rst.txt | 33 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 …]
|
| A D | security-hardening.rst.txt | 11 Part of the security of a platform is handling errors correctly, as described in
|
| A D | coding-style.rst.txt | 170 adopted to follow MISRA guidelines more closely and to help prevent errors.
|
| /trusted-firmware-a/drivers/brcm/emmc/ |
| A D | emmc_csl_sdcard.c | 53 static int err_recovery(struct sd_handle *handle, uint32_t errors);
815 static int err_recovery(struct sd_handle *handle, uint32_t errors) in err_recovery() argument
825 if (errors & SD_CMD_ERROR_INT) in err_recovery()
829 if (errors & SD_DAT_ERROR_INT) in err_recovery()
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/threat_model/ |
| A D | threat_model.rst.txt | 548 | | errors can arise. Memory corruption is a dangerous |
554 | | | Some of the errors include integer overflow, |
559 | | errors in release builds. |
598 | | programming errors in debug builds. Other types of |
599 | | errors are handled through condition checks that |
|
| A D | threat_model_spm.rst.txt | 301 | ``Threat`` | *An attacker may attempt injecting errors by the |
|
| /trusted-firmware-a/docs/threat_model/ |
| A D | threat_model.rst | 548 | | errors can arise. Memory corruption is a dangerous |
554 | | | Some of the errors include integer overflow, |
559 | | errors in release builds. |
598 | | programming errors in debug builds. Other types of |
599 | | errors are handled through condition checks that |
|
| A D | threat_model_spm.rst | 301 | ``Threat`` | *An attacker may attempt injecting errors by the |
|
| /trusted-firmware-a/docs/build/latex/ |
| A D | trustedfirmware-a.aux | 790 \@writefile{toc}{\contentsline {subsubsection}{Using CASSERT to check for compile time data errors}…
791 …-cassert-to-check-for-compile-time-data-errors}{{3.5.5}{125}{Using CASSERT to check for compile ti…
792 \@writefile{toc}{\contentsline {subsubsection}{Using assert() to check for programming errors}{126}…
793 …ines:using-assert-to-check-for-programming-errors}{{3.5.5}{126}{Using assert() to check for progra…
794 \@writefile{toc}{\contentsline {subsubsection}{Handling integration errors}{126}{subsubsection*.257…
795 …abel{process/coding-guidelines:handling-integration-errors}{{3.5.5}{126}{Handling integration erro…
796 \@writefile{toc}{\contentsline {subsubsection}{Handling recoverable errors}{126}{subsubsection*.258…
797 …abel{process/coding-guidelines:handling-recoverable-errors}{{3.5.5}{126}{Handling recoverable erro…
798 \@writefile{toc}{\contentsline {subsubsection}{Handling unrecoverable errors}{127}{subsubsection*.2…
799 …l{process/coding-guidelines:handling-unrecoverable-errors}{{3.5.5}{127}{Handling unrecoverable err…
|
| A D | trustedfirmware-a.tex | 11769 \subsubsection{Handling integration errors}
11790 \subsubsection{Handling recoverable errors}
11835 \subsubsection{Handling unrecoverable errors}
11867 Examples of unexpected unrecoverable errors:
11896 Examples of expected unrecoverable errors:
17211 paradigm for handling platform errors: exceptions resulting from errors are
17270 A handler to probe error records for errors;
48450 errors in release builds.
59706 Trap all asynchronous bus errors to EL3
62909 interprets as errors.
[all …]
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/ |
| A D | change-log.md.txt | 1401 - Filter errors related to clock gate permissions
1524 - Fixed compilation errors with -O0 compile option
1880 - Fixed timeout errors caused by excess error logging
1900 - Fixed compilation errors caused by increase in BL2 size
2312 - imx: Fix shift-overflow errors, the rdc memory region slot's offset,
2372 - Add compile-time errors for HW_ASSISTED_COHERENCY flag
2451 Trap all asynchronous bus errors to EL3
2850 - "Warnings as errors" (Werror) can be disabled using `E=0`
3802 interprets as errors.
4017 the TF-A build system interprets as errors.
[all …]
|
| /trusted-firmware-a/docs/ |
| A D | change-log.md | 1401 - Filter errors related to clock gate permissions
1524 - Fixed compilation errors with -O0 compile option
1880 - Fixed timeout errors caused by excess error logging
1900 - Fixed compilation errors caused by increase in BL2 size
2312 - imx: Fix shift-overflow errors, the rdc memory region slot's offset,
2372 - Add compile-time errors for HW_ASSISTED_COHERENCY flag
2451 Trap all asynchronous bus errors to EL3
2850 - "Warnings as errors" (Werror) can be disabled using `E=0`
3802 interprets as errors.
4017 the TF-A build system interprets as errors.
[all …]
|
| /trusted-firmware-a/docs/plat/marvell/armada/ |
| A D | build.rst | 185 to running Linux kernel and makes correctable errors as fatal aborts.
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/plat/marvell/armada/ |
| A D | build.rst.txt | 185 to running Linux kernel and makes correctable errors as fatal aborts.
|
| /trusted-firmware-a/docs/getting_started/ |
| A D | build-options.rst | 211 - ``E``: Boolean option to make warnings into errors. Default is 1.
|
| A D | porting-guide.rst | 1051 Possible errors reported by the generic code are:
2963 Uncontainable errors, the intention of this function is to initiate orderly
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/getting_started/ |
| A D | build-options.rst.txt | 211 - ``E``: Boolean option to make warnings into errors. Default is 1.
|
| /trusted-firmware-a/docs/design/ |
| A D | interrupt-framework-design.rst | 344 library APIs. The handler should treat all error conditions as critical errors
|
| /trusted-firmware-a/docs/build/TF-A_2.5/_sources/design/ |
| A D | interrupt-framework-design.rst.txt | 344 library APIs. The handler should treat all error conditions as critical errors
|