Lines Matching refs:be

16 versions (8.X, 9.X) to which they apply can be found in `Feature_description`_
457 higher exception levels, other features might be used by TF-A code itself.
477 If the feature flag is set to 2, support for the feature will be compiled in,
478 but its existence will be checked at runtime, so it works on CPUs with or
490 b) a feature is to be used by EL3 itself
501   - The flag's name should be in the form ``ENABLE_FEAT_ABC``.
510   - Add any constraints in ``make_helpers/constraints.mk``. This will usually be
512     be found in the main description of the feature in the Arm ARM.
516   A pair of functions must be defined in the form of ``is_feat_abc_present()``
520   - The ``_supported`` variant is the one that should usually be used. If common
521     code is to use it, a corresponding AArch32 version should be provided. It
522     should return ``false`` if AArch32 is not to be supported.
524   - In rare occasions, the feature must be checked in assembly. A
525     ``is_feat_abc_present_asm`` macro must be added to
530 - Add support for the feature. This will be very feature specific and exact code
531   will depend on why support is being added. Usually, support will be a few
536     file in ``lib/extensions/abc/``. Functions in this file must be named
537     similar to other features. Those are likely to be ``abc_enable()``,
541    for lower ELs, access must be enabled for at least NS world, preferably all
545    ``CPTR_EL3``, or ``MPAM3_EL3``, those must be added to the appropriate list
547    ``ARCH_FEATURE_AVAILABILITY``. This must also be done in the
551  - If the feature comes with registers, those should be context switched if
569   ``run_config/fvp-aemv8a.all``. Mandatory features are expected to be covered
573   be done if there are observable effects from lower ELs like register traps. It