Searched refs:feature (Results 1 – 25 of 37) sorted by relevance
12
| /trusted-firmware-a-3.4.0/docs/design_documents/ |
| D | context_mgmt_rework.rst | 40 the library will not be responsible for CPU feature enablement for
72 (4) **Allow more flexibility for Dispatchers to select feature set to save and restore**
78 both Realm and Secure world will have the same feature set enabled from
84 save and restore routine corresponding to Arch feature. The memory allocation
87 context memory allocated but not used at runtime based on feature detection
88 at runtime or the platform owner has decided not to enable the feature
148 enabled for the sake of robustness. Another example is, if the MTE feature
149 is enabled for a particular world, this feature will be enabled for Root world
151 be expecting this feature to be enabled and may cause unwanted side-effects
157 Architectural feature(s) or do some security hardening, it might need
[all …]
|
| /trusted-firmware-a-3.4.0/docs/getting_started/ |
| D | build-options.rst | 34 one or more feature modifiers. This option has the form ``[no]feature+...``
36 ``-march=armvX[.Y]-a+[no]feature+...``. See compiler's documentation for the
37 list of supported feature modifiers.
179 this feature in the Secure world and MTE is enabled at ELX. This flag can
204 feature as per TBBR.
228 This is an optional architectural feature available on v8.4 onwards. Some
230 enable this feature on those systems as well. Default is 0.
261 to align with the ``FEATURE_DETECTION`` mechanism. It is an optional feature
267 extension. ``FEAT_AMUv1p1`` is an optional feature available on Arm v8.6
274 optional feature available on Arm v8.0 onwards. This flag can take values
[all …]
|
| D | image-terminology.rst | 99 :ref:`Realm Management Extension (RME)` feature is enabled. If a path to RMM
|
| /trusted-firmware-a-3.4.0/docs/components/measured_boot/ |
| D | event_log.rst | 27 and this property should be removed when this feature is supported.
|
| /trusted-firmware-a-3.4.0/docs/plat/marvell/armada/ |
| D | porting.rst | 48 feature is used for boot loader recovery by booting from a valid flash-image
62 To disable this feature make sure the struct skip_image is not implemented.
140 …- if different comphy index is used for specific feature, move it to proper table entry and then a…
|
| /trusted-firmware-a-3.4.0/docs/plat/ |
| D | imx8.rst | 4 The i.MX 8 series of applications processors is a feature- and
|
| D | synquacer.rst | 96 any version of gcc >= 5 will support this feature and may be used to build EDK2.
|
| D | rpi4.rst | 14 not seem to feature a secure memory controller of any kind, so portions of
|
| D | allwinner.rst | 58 This option defaults to 1 on SoCs that feature an SCP. If no SCP firmware
|
| /trusted-firmware-a-3.4.0/docs/components/ |
| D | debugfs-design.rst | 10 The *DebugFS* feature is primarily aimed at exposing firmware debug data to
89 - Due to the nature of the exposed data, the feature is considered experimental
|
| D | xlat-tables-lib-v2-design.rst | 40 be applied to all versions of the xlat_* libs, future feature enhancements will
187 The library optionally supports dynamic memory mapping. This feature may be
199 When the dynamic memory mapping feature is disabled, only static regions exist.
201 The dynamic memory mapping feature may be used to map and unmap transient memory
209 Although this feature provides some level of dynamic memory allocation, this
237 As explained earlier in this document, when the dynamic mapping feature is
|
| D | firmware-update.rst | 7 This document describes the design of the Firmware Update (FWU) feature, which
11 platform. This feature functions even when the current firmware in the system
50 The primary requirements of the FWU feature are:
|
| D | romlib-design.rst | 10 The "library at ROM" feature allows platforms to build a library of functions to
|
| /trusted-firmware-a-3.4.0/docs/about/ |
| D | features.rst | 4 This page provides an overview of the current |TF-A| feature set. For a full
76 This feature is now incorporated inside the firmware configuration framework
|
| /trusted-firmware-a-3.4.0/docs/design/ |
| D | trusted-board-boot.rst | 4 The Trusted Board Boot (TBB) feature prevents malicious firmware from running on
191 BL1 and BL2 code, and in tool code on the host build machine. The feature is
237 implement the optional firmware encryption feature. This feature can be
|
| D | reset-design.rst | 112 ``RVBAR_EL3`` register at start-up. This feature is provided on the Base FVP
|
| /trusted-firmware-a-3.4.0/docs/process/ |
| D | commit-style.rst | 57 | ``feat`` | A new feature |
69 | ``refactor`` | A code change that neither fixes a bug nor adds a feature |
|
| /trusted-firmware-a-3.4.0/docs/security_advisories/ |
| D | security-advisory-tfv-2.rst | 30 Given that TF does not currently contain support for this feature (for example,
|
| D | security-advisory-tfv-3.rst | 34 This feature does not work correctly for AArch64 images executing at Secure EL1.
|
| D | security-advisory-tfv-9.rst | 103 this vulnerability for Cortex-A72 CPU versions that support the CSV2 feature
|
| D | security-advisory-tfv-4.rst | 54 introduced AArch32 support for the Trusted Board Boot (TBB) feature. Before
|
| D | security-advisory-tfv-1.rst | 27 available after cold reset to support the Firmware Update (FWU) feature (also
|
| /trusted-firmware-a-3.4.0/ |
| D | Makefile | 163 $(warning DEBUGFS experimental feature is enabled.)
760 $(info PSA_FWU_SUPPORT is an experimental feature)
764 $(info FEATURE_DETECTION is an experimental feature)
832 $(info DRTM_SUPPORT is an experimental feature)
|
| /trusted-firmware-a-3.4.0/services/std_svc/sdei/ |
| D | sdei_main.c | 939 static uint64_t sdei_features(unsigned int feature) in sdei_features() argument
941 if (feature == SDEI_FEATURE_BIND_SLOTS) { in sdei_features()
|
| /trusted-firmware-a-3.4.0/docs/components/fconf/ |
| D | index.rst | 124 feature/data abstracted.
|
12
