Lines Matching refs:feature

93 3. **Flexibility for Dispatchers to select desired feature set to save and restore**
95 Each feature is supported with a helper function ``is_feature_supported(void)``,
97 feature set, and thereby save and restore the configuration associated with them.
101 TF-A supports four states for feature enablement at EL3, to make them available
110 A pattern is established for feature enablement behavior.
111 Each feature must support the 3 possible values with rigid semantics.
113 - **FEAT_STATE_DISABLED** - all code relating to this feature is always skipped.
114   Firmware is unaware of this feature.
116 - **FEAT_STATE_ALWAYS** - all code relating to this feature is always executed.
117   Firmware expects this feature to be present in hardware.
119 - **FEAT_STATE_CHECK** - same as ``FEAT_STATE_ALWAYS`` except that the feature's
133     - Any feature that impacts the generation of page tables must be symmetric.
134     - Any feature access which does not trap to EL3 should be symmetric.
156    context for different security states alongside high level feature enablement
449 Pointer Authentication feature is enabled by default for Non-Secure world and
474 Further, a pattern is established for feature enablement code (AArch64).
475 Each feature implements following APIs as applicable:
476 Note: (``xxx`` is the name of the feature in the APIs)
481   functions to enable the feature for the passed context only. To be called in
484 - ``xxx_init_el3()`` - optional function to enable the feature in-place in any EL3
489 - ``xxx_init_el2_unused()`` - optional function to enable the feature in-place