| /rk3399_ARM-atf/ |
| H A D | .commitlintrc.js | 46 const types = getTypes(changelog.sections).sort(); /* Sort alphabetically */ constant
67 "type-enum": [2, "always", types], /* Error */
|
| H A D | .versionrc.cjs | 15 * The types and scopes accepted by both Commitlint and Commitizen are defined by the changelog
59 const types = getTypes(changelog.sections);
70 "types": types,
|
| H A D | poetry.lock | 1034 …", "flake8-simplify", "isort", "mypy (>=0.981)", "sphinx-lint", "types-requests", "types-typed-ast…
|
| /rk3399_ARM-atf/include/export/ |
| H A D | README | 13 - They must not rely on any type definitions other that <stdint.h> types defined
24 - They should avoid using integer types with architecture-dependent widths
25 (e.g. long, uintptr_t, pointer types) where possible. (Some existing export
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | index.rst | 8 There exists many types of FVPs. This page provides details on how to build and
|
| /rk3399_ARM-atf/docs/process/ |
| H A D | coding-guidelines.rst | 172 | ``vsnprintf`` | Caution | inspect va_list match types |
344 Use of built-in *C* and *libc* data types
351 - Where possible, use the built-in *C* data types for variable storage (for
353 types. Most code is typically only concerned with the minimum size of the
354 data stored, which the built-in *C* types guarantee.
356 - Avoid using the exact-size standard *C99* types in general (for example,
381 rules (10.X), where signed and unsigned types are considered different
382 essential types. Choosing the correct type will aid this. MISRA static
386 - For pointer types:
399 includes pointers to types that are abstracted away from the known API and
[all …]
|
| H A D | commit-style.rst | 55 The following `types` are permissible and are strictly enforced:
|
| /rk3399_ARM-atf/docs/plat/marvell/armada/ |
| H A D | porting.rst | 108 board types. Therefore each board type can have its own list of values for
131 Not all comphy types are already reworked to support the PHY porting
133 comphy types.
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | dtpm_drivers.rst | 21 The design implemented in TF-A supports multiple types of TPM hardware interfaces
22 and hardware bus types in order to be compatible with different platforms.
|
| H A D | cmake_framework.rst | 123 types: the former is only a CMake domain option, the latter is only a C language
|
| H A D | measured_boot_poc.rst | 27 SHA algorithms) and they might also use different types of TPM services
|
| H A D | psci_osi_mode.rst | 69 heterogeneous systems like big.LITTLE, where different processor types can have
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | granule-protection-tables-design.rst | 163 The public APIs and types can be found in ``include/lib/gpt_rme/gpt_rme.h`` and this
184 by the GTSI to find the tables and transition granules between PAS types.
193 The values allowed by the API for PPS and PGS are enumerated types
|
| H A D | platform-interrupt-controller-API.rst | 136 returns *true* for all interrupt types.
139 ``INTR_TYPE_NS``. Return value for other types depends on the value of build
|
| H A D | realm-management-extension.rst | 34 types.
|
| H A D | el3-spmc.rst | 173 The specification also defines the types of data that can be passed.
|
| H A D | context-management-library.rst | 395 The public APIs and types can be found in ``include/lib/el3_runtime/context_management.h``
|
| /rk3399_ARM-atf/docs/threat_model/firmware_threat_model/ |
| H A D | threat_model_el3_spm.rst | 80 - Threat types
116 Threat types
521 | | are recommended ways to mitigate Spectre types of |
|
| H A D | threat_model.rst | 39 The :ref:`Threat Model for TF-A with Arm CCA support` covers these types of
181 or more of these types: ``Spoofing``, ``Tampering``, ``Repudiation``,
464 | | programming errors in debug builds. Other types of |
|
| /rk3399_ARM-atf/docs/components/fconf/ |
| H A D | index.rst | 116 The framework differentiates two types of properties:
|
| /rk3399_ARM-atf/docs/design/ |
| H A D | interrupt-framework-design.rst | 29 Interrupt types
48 The following constants define the various interrupt types in the framework
86 types are supported for GIC version 2.0 (Arm GICv2) (see `Assumptions in
185 Effect of mapping of several interrupt types to one signal
191 that security state. This means that all the other interrupt types using the
196 Secure-EL0, both the EL3 and the non secure interrupt types map to the FIQ
207 #. Although the framework has support for 2 types of secure interrupts (EL3
360 The ``type`` parameter can be one of the three interrupt types listed above i.e.
|
| H A D | auth-framework.rst | 122 Image types
399 the following ASN.1 types.
484 - ``_type``: one of the types described above.
729 authentication parameters. Three types of images are currently supported:
|
| /rk3399_ARM-atf/licenses/ |
| H A D | LICENSE-APACHE-2.0.txt | 34 and conversions to other media types.
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | rt-svc-writers-guide.rst | 63 *Table 1: Service types and their corresponding Owning Entity Numbers*
|
| /rk3399_ARM-atf/docs/threat_model/ |
| H A D | supply_chain_threat_model.rst | 345 | Threat and | | TF-A has two types of dependencies: those that are copied |
|