| /rk3399_ARM-atf/docs/ |
| H A D | architecture_features.rst | 459 Most of the feature flags defined in the TF-A build system are allowed to take
467 feature present at runtime.
469 When setting the flag to 0, the feature is disabled during compilation, and the
473 If it is defined to 1, the code will use the feature unconditionally, so the CPU
474 is expected to support that feature. The FEATURE_DETECTION debug feature, if
477 If the feature flag is set to 2, support for the feature will be compiled in,
479 without the feature. This is mostly useful for platforms which either support
483 Adding support for a new feature
486 Adding support for a feature is required when:
488 a) a feature is added to the architecture and it includes controls at EL3
[all …]
|
| /rk3399_ARM-atf/make_helpers/ |
| H A D | constraints.mk | 100 $(warning DEBUGFS experimental feature is enabled.)
213 $(info FEATURE_DETECTION is an experimental feature)
396 $(info DRTM_SUPPORT is an experimental feature)
400 $(warning HOB_LIST is an experimental feature)
404 $(info TRANSFER_LIST is an experimental feature)
408 $(info PSA_CRYPTO is an experimental feature)
412 $(info DICE_PROTECTION_ENVIRONMENT is an experimental feature)
416 $(warning LFA_SUPPORT is an experimental feature)
442 $(info FEAT_IDTE3 is an experimental feature)
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | build-options.rst | 35 one or more feature modifiers. This option has the form ``[no]feature+...``
37 ``-march=armvX[.Y]-a+[no]feature+...``. See compiler's documentation for the
38 list of supported feature modifiers.
229 feature as per TBBR.
236 PMU). ``FEAT_MTPMU`` is an optional feature available on Armv8.6 onwards.
256 otherwise. To use this feature, platforms will have to create the function
289 ``ENABLE_FEAT`` mechanism. This is an optional architectural feature
291 and this option can be used to enable this feature on those systems as well.
295 extension. ``FEAT_AMUv1p1`` is an optional feature available on Arm v8.6
302 cannot be used by code. This is an optional architectural feature available on v8.0
[all …]
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | context-management-library.rst | 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.
[all …]
|
| H A 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
|
| H A D | ras.rst | 95 **Delegated SError exception injection** feature introduced for EL3.
108 - **ENABLE_FEAT_RAS**: Enable RAS extension feature at EL3.
118 RAS feature has dependency on some other TF-A build flags
121 - **FAULT_INJECTION_SUPPORT**: Required for testing RAS feature on fvp platform
|
| H A D | xlat-tables-lib-v2-design.rst | 171 The library optionally supports dynamic memory mapping. This feature may be
183 When the dynamic memory mapping feature is disabled, only static regions exist.
185 The dynamic memory mapping feature may be used to map and unmap transient memory
193 Although this feature provides some level of dynamic memory allocation, this
220 As explained earlier in this document, when the dynamic mapping feature is
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | features.rst | 4 This page provides an overview of the current |TF-A| feature set. For a full
92 This feature is now incorporated inside the firmware configuration framework
114 A feature is considered experimental when still in development or isn't known
119 A feature is no longer considered experimental when it is generally agreed
120 the said feature has reached a level of maturity and quality comparable to
|
| /rk3399_ARM-atf/plat/mediatek/drivers/thermal/inc/ |
| H A D | thermal_lvts.h | 24 #define IS_ENABLE(lvts_data, feature) \ argument
25 (lvts_data->feature_bitmap & feature)
|
| /rk3399_ARM-atf/docs/components/measured_boot/ |
| H A D | event_log.rst | 27 and this property should be removed when this feature is supported.
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A 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…
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | imx8.rst | 4 The i.MX 8 series of applications processors is a feature- and
|
| H A D | rpi5.rst | 12 not seem to feature a secure memory controller of any kind, so portions of
|
| H A D | synquacer.rst | 96 any version of gcc >= 5 will support this feature and may be used to build EDK2.
|
| /rk3399_ARM-atf/docs/security_advisories/ |
| H A D | security-advisory-tfv-12.rst | 32 Hardware Page Aggregation (HPA) feature. In environments utilizing virtualization,
|
| H A D | security-advisory-tfv-2.rst | 30 Given that TF does not currently contain support for this feature (for example,
|
| H A D | security-advisory-tfv-3.rst | 34 This feature does not work correctly for AArch64 images executing at Secure EL1.
|
| H A D | security-advisory-tfv-9.rst | 103 this vulnerability for Cortex-A72 CPU versions that support the CSV2 feature
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | security-hardening.rst | 142 `getc()` feature, which allows the firmware to read characters from the
143 console. Keeping this feature enabled is considered dangerous from a security
|
| H A D | commit-style.rst | 60 | ``feat`` | A new feature |
72 | ``refactor`` | A code change that neither fixes a bug nor adds a feature |
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | trusted-board-boot.rst | 4 The `Trusted Board Boot` (TBB) feature prevents malicious firmware from running
264 BL1 and BL2 code, and in tool code on the host build machine. The feature is
311 implement the optional firmware encryption feature. This feature can be
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_fw_update_and_recovery.rst | 8 the feature PSA firmware update or TBBR firmware update or both enabled.
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | fvp-support.rst | 7 platforms, largely used for early feature development. They offer a large
|
| /rk3399_ARM-atf/services/std_svc/sdei/ |
| H A D | sdei_main.c | 971 static uint64_t sdei_features(unsigned int feature) in sdei_features() argument
973 if (feature == SDEI_FEATURE_BIND_SLOTS) { in sdei_features()
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | psci-performance-instr.rst | 37 This feature is enabled with the Boolean flag ``ENABLE_PMF``.
|