Lines Matching refs:handler

44 RAS Framework in TF-A allows the platform to define an external abort handler and to
82 * The handler reflects pending async EAs back to the lower EL if the EA routing model is KFH
136    Inject External aborts(sync/async) which traps in EL3, FVP has a handler which gracefully
200 -  A handler to probe error records for errors;
201 -  When the probing identifies an error, a handler to handle it;
209 records for error, and invoke the appropriate handler to handle it.
220     ERR_RECORD_MEMMAP_V1(base_addr, size_num_k, probe, handler, aux)
226     ERR_RECORD_SYSREG_V1(idx_start, num_idx, probe, handler, aux)
228 The probe handler must have the following prototype:
235 The probe handler must return a non-zero value if an error was detected, or 0
237 information resulting from probe to the error handler (see `below`__). For
242 The error handler must have the following prototype:
251 ``cookie``, and ``handle`` parameters from the :ref:`top-level exception handler
310 condition arises, the Arm RAS extensions only require for handler to perform
325 Double faults are fatal, and terminate at the platform double fault handler, and
334 ``plat_ea_handler``, the External Abort handler in EL3. When ``ENABLE_FEAT_RAS``
336 top-level RAS exception handler. ``ras_ea_handler`` is responsible for iterating
338 identified, look up and invoke the corresponding error handler.
348 with the interrupt number. That error handler for that record is then invoked to