Lines Matching refs:handler

44 RAS Framework in TF-A allows the platform to define an external abort handler and to
107    Inject External aborts(sync/async) which traps in EL3, FVP has a handler which gracefully
171 -  A handler to probe error records for errors;
172 -  When the probing identifies an error, a handler to handle it;
180 records for error, and invoke the appropriate handler to handle it.
191     ERR_RECORD_MEMMAP_V1(base_addr, size_num_k, probe, handler, aux)
197     ERR_RECORD_SYSREG_V1(idx_start, num_idx, probe, handler, aux)
199 The probe handler must have the following prototype:
206 The probe handler must return a non-zero value if an error was detected, or 0
208 information resulting from probe to the error handler (see `below`__). For
213 The error handler must have the following prototype:
222 ``cookie``, and ``handle`` parameters from the :ref:`top-level exception handler
281 condition arises, the Arm RAS extensions only require for handler to perform
296 Double faults are fatal, and terminate at the platform double fault handler, and
305 ``plat_ea_handler``, the External Abort handler in EL3. When ``ENABLE_FEAT_RAS``
307 top-level RAS exception handler. ``ras_ea_handler`` is responsible for iterating
309 identified, look up and invoke the corresponding error handler.
319 with the interrupt number. That error handler for that record is then invoked to