| /rk3399_ARM-atf/make_helpers/ |
| H A D | march.mk | 88 arch-features = ${ARM_ARCH_FEATURE}
97 arch-features := $(arch-features)+pauth-lr
104 ifneq ($(arch-features), none)
106 arch-features := $(subst none+,,$(arch-features))
107 march-directive := $(march-directive)+$(arch-features)
109 $(info Arm Architecture Features specified: $(subst +, ,$(arch-features)))
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | index.rst | 5 platform's needs, providing a holistic threat model covering all of its features
10 documents typically focus on specific features not covered in the core document.
12 As the TF-A codebase evolves and new features get added, these threat model
19 features within the project, we have not reached that point yet. We expect
|
| H A D | threat_model_arm_cca.rst | 75 - No experimental features are enabled. These are typically incomplete features,
77 come from them. It is not recommended to use these features in production
|
| H A D | threat_model_fw_update_and_recovery.rst | 66 2. The FWU metadata features a field indicating the firmware's status, either
|
| /rk3399_ARM-atf/services/std_svc/drtm/ |
| H A D | drtm_main.h | 34 #define DL_ARGS_GET_DMA_PROT_TYPE(a) (((a)->features >> 3) & 0x7U)
35 #define DL_ARGS_GET_PCR_SCHEMA(a) (((a)->features >> 1) & 0x3U)
83 uint32_t features; member
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | index.rst | 8 features
|
| H A D | features.rst | 5 description of these features and their implementation details, please see
11 Current features
111 Experimental features
121 other features that have been integrated into products.
141 - Ongoing support for new architectural features, CPUs and System IP.
|
| /rk3399_ARM-atf/docs/ |
| H A D | architecture_features.rst | 4 The Arm architecture evolves through versioning, with new architectural features being introduced
5 almost every year listed in `Feature_description`_. While most of these features require no control
7 Exception Levels. For features with EL3 controls, it is relatively straightforward to examine the
8 code and determine whether TF-A support them. However, for features that are transparent to EL3, it
13 architectural features within TF-A.
15 This document organizes features according to the yearly updates, while the specific architecture
455 The Arm architecture defines several architecture extension features, named
456 FEAT_xxx in the architecure manual. Some of those features require setup code in
457 higher exception levels, other features might be used by TF-A code itself.
511 other features which this feature depends on or is incompatible with and can
[all …]
|
| H A D | index.rst | 59 The **About** chapter gives a high-level overview of |TF-A| features as well as
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | context-management-library.rst | 35 and execute any of the architectural features.
41 the architectural features enabled in the former security state will be unconditionally
125 architectural features (features will be symmetrical). However, there are
126 cases where this is impractical to achieve. Only some features can be
132 - All mandatory features must be symmetric.
138 TF-A caters for mismatched features, however, this is not regularly tested
139 for all features and may not work as expected, even without considering OS
242 trace features can vary across CPUs, these ID registers are cached
470 Functions that allow the enabling and disabling of architectural features for
478 - ``is_feat_xxx_supported()`` and ``is_feat_xxx_present()`` - mandatory for all features.
[all …]
|
| /rk3399_ARM-atf/docs/components/spd/ |
| H A D | tlk-dispatcher.rst | 29 TLK features include:
33 • Added TrustZone features
|
| /rk3399_ARM-atf/drivers/arm/ethosn/ |
| H A D | ethosn_smc.c | 200 uint32_t features) in ethosn_configure_aux_features() argument
204 if (features & ETHOSN_AUX_FEAT_LEVEL_IRQ) { in ethosn_configure_aux_features()
208 if (features & ETHOSN_AUX_FEAT_STASHING) { in ethosn_configure_aux_features()
|
| /rk3399_ARM-atf/docs/plat/arm/corstone1000/ |
| H A D | index.rst | 4 Some of the features of the Corstone1000 platform referenced in TF-A include:
|
| /rk3399_ARM-atf/plat/arm/board/automotive_rd/platform/rd1ae/ |
| H A D | platform.mk | 9 $(warning Platform ${PLAT} is deprecated. Some of the features might not work as expected)
|
| /rk3399_ARM-atf/include/drivers/ |
| H A D | raw_nand.h | 101 uint16_t features; member
|
| /rk3399_ARM-atf/docs/plat/arm/tc/ |
| H A D | index.rst | 4 Some of the features of TC platform referenced in TF-A include:
|
| /rk3399_ARM-atf/docs/plat/arm/automotive_rd/ |
| H A D | rd1ae.rst | 4 Some of the features of the RD-1 AE platform referenced in TF-A include:
|
| H A D | rdaspen.rst | 4 The RD-Aspen platform, as referenced in TF-A, includes the following features:
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | imx8ulp.rst | 8 The i.MX 8ULP family of processors features NXP’s advanced implementation of the
|
| H A D | socionext-uniphier.rst | 77 Optional features
|
| /rk3399_ARM-atf/ |
| H A D | .versionrc.cjs | 63 …"header": "# Change Log & Release Notes\n\nThis document contains a summary of the new features, c…
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | trusted-board-boot-build.rst | 4 Trusted Board Boot primarily consists of the following two features:
10 images with support for these features:
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | performance-monitoring-unit.rst | 41 `Arm ARM`_ for a detailed description of ARMv8.5-PMU features.
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | tb_fw_bindings.rst | 144 features such as certificate hierarchies, rollback protection, and root-of-trust
|
| /rk3399_ARM-atf/drivers/mtd/nand/ |
| H A D | raw_nand.c | 317 if ((page.features & ONFI_FEAT_BUS_WIDTH_16) != 0U) { in nand_read_param_page()
|