| /trusted-firmware-m-latest/secure_fw/partitions/crypto/ |
| D | Kconfig.comp | 32 for EC signing by attest module.
49 bool "PSA Crypto random number generator module"
53 bool "PSA Crypto Key module"
57 bool "PSA Crypto AEAD module"
61 bool "PSA Crypto MAC module"
65 bool "PSA Crypto Hash module"
69 bool "PSA Crypto Cipher module"
73 bool "PSA Crypto asymmetric key signature module"
77 bool "Enable PSA Crypto asymmetric key encryption module"
81 bool "PSA Crypto key derivation module"
|
| /trusted-firmware-m-latest/secure_fw/partitions/initial_attestation/ |
| D | attest_boot_data.c | 163 static int32_t attest_get_tlv_by_module(uint8_t module, in attest_get_tlv_by_module() argument
195 if (GET_IAS_MODULE(tlv_entry.tlv_type) == module) { in attest_get_tlv_by_module()
293 uint8_t module = 0; in attest_encode_sw_components_array()
305 for (module = 0; module < SW_MAX; ++module) { in attest_encode_sw_components_array()
312 found = attest_get_tlv_by_module(module, &tlv_id, in attest_encode_sw_components_array()
|
| /trusted-firmware-m-latest/platform/ext/target/cypress/psoc64/libs/core-lib/include/ |
| D | cy_result.h | 126 #define CY_RSLT_CREATE(type, module, code) \ argument
127 ((((module) & CY_RSLT_MODULE_MASK) << CY_RSLT_MODULE_POSITION) | \
|
| /trusted-firmware-m-latest/docs/platform/lairdconnectivity/bl5340_dvk_cpuapp/ |
| D | README.rst | 5 for the evaluation and development on the Laird Connectivity BL5340 module
8 The BL5340 is a module with a dual-core nRF5340 SoC based on the Arm®
65 * SWD debug for the BL5340 module
80 The nRF Command-line Tools allow you to control your BL5340 module from the
107 * Erase the flash memory in the BL5340 module:
140 * Erase the flash memory in the BL5340 module:
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/Core/Include/ |
| D | tz_context.h | 51 TZ_MemoryId_t TZ_AllocModuleContext_S (TZ_ModuleId_t module);
|
| /trusted-firmware-m-latest/docs/cmake/ |
| D | FindSphinx.cmake | 13 #This module checks availability of the Sphinx document generator
17 #method this module expects sphix-build to be either available on the PATH,
90 #Set "standard" find module return values
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/Core/Template/ARMv8-M/ |
| D | tz_context.c | 86 TZ_MemoryId_t TZ_AllocModuleContext_S (TZ_ModuleId_t module) { in TZ_AllocModuleContext_S() argument
89 (void)module; // Ignore (fixed Stack size) in TZ_AllocModuleContext_S()
|
| /trusted-firmware-m-latest/docs/integration_guide/services/ |
| D | tfm_crypto_integration_guide.rst | 26 - An init module ``secure_fw/partitions/crypto/crypto_init.c`` that implements
33 - An alloc module ``secure_fw/partitions/crypto/crypto_alloc.c`` that manages
37 - A library abstraction module ``secure_fw/partitions/crypto/crypto_library.c``
83 - ``crypto_init.c`` : Init module for the service. The modules stores also the
97 the contexts is much simpler (i.e. just an handle), and the Alloc module
99 - ``tfm_crypto_api.c`` : This module is contained in ``interface/src`` and
101 This module allows a configuration option ``CONFIG_TFM_CRYPTO_API_RENAME``
107 - ``tfm_mbedcrypto_alt.c`` : This module is specific to the Mbed TLS [3]_
|
| /trusted-firmware-m-latest/docs/contributing/ |
| D | code_review_guide.rst | 124 - R5.1 Put the ``interface header`` of one module in the ``include`` folder
125 under the root of this module. Deeper sub-folders can not have ``include``
126 folders, which means only one ``include`` is allowed for one module.
141 - R5.6 The module's ``include`` folder needs to be added into referencing
142 module's header searching path.
144 - R5.7 The module's ``include`` folder and the root folder needs to be added
149 ``include`` folder and the module folder.
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Source/ |
| D | CV_Report.c | 325 test_report.assertions.info.passed[TAS->passed].module = fn;
331 test_report.assertions.info.failed[TAS->failed].module = fn;
337 test_report.assertions.info.warnings[TAS->warnings].module = fn;
|
| /trusted-firmware-m-latest/secure_fw/partitions/platform/ |
| D | Kconfig.comp | 28 bool "Disable Non-volatile counter module"
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Include/ |
| D | CV_Report.h | 32 const char *module; /* Module name */ member
|
| /trusted-firmware-m-latest/docs/design_docs/services/ |
| D | tfm_crypto_design.rst | 43 …| Client API interface | This module exports the PSA Crypto API to be callable from the| ``…
53 …| Init module | This module handles the initialisation of the service objects | ``…
61 …| | This module is in charge of providing an ID of the caller of | …
65 …| Alloc module | This module handles the allocation of contexts for multipart | ``…
85 …| Backend library abstraction | This module contains several APIs to abstract the interface | ``…
100 …| | which expose each module's interface. The header available in | …
263 …| | | | module) and initializes the `b…
337 … | CMake build | When enabled, the correspoding shim layer module and relative | De…
|
| D | tfm_fwu_service.rst | 41 …| Client API interface | This module exports the client API of PSA Firmware Update to | ``…
46 …| NSPE client API interface | This module exports the client API of PSA Firmware Update to | ``…
49 …| IPC request handlers | This module handles all the secure requests in IPC model. | ``…
53 …| Shim layer between FWU and | This module provides the APIs with the functionality of | ``…
57 …| Shim layer example based on | This module is the implementation of the shim layer between | ``…
|
| /trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/CoreValidation/Project/ |
| D | validation.xsl | 28 <xsl:variable name="file" select="module"/>
|
| /trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/codesafe/src/psa_driver_api/ |
| D | psa_driver_api_design.rst | 51 contain the types associated to the driver. Any module that does not need to
53 treat each object as an opaque pointer, while any module that needs access to
98 DRBG. This module has an explicit dependency on the mbedTLS DRBG software
133 the driver module integration into the PSA Crypto driver core. The following
173 * ``mbedtls_drbg``: The module currently relies on a software implementation of
|
| /trusted-firmware-m-latest/docs/platform/cypress/psoc64/libs/core-lib/ |
| D | RELEASE.md | 50 * Added new module identifiers to cy_result.h
56 * Added new module IDs in cy_result.h
|
| /trusted-firmware-m-latest/docs/releases/ |
| D | 1.0.rst | 115 by SST module should not be updatable but after reboot, the update seems
132 the SST module when Flash data is inconsistent.
|
| D | 1.5.0.rst | 25 - ITS enhancement for harden ITS module against invalid data in Flash.
|
| /trusted-firmware-m-latest/docs/integration_guide/ |
| D | non-secure_client_extension_integration_guide.rst | 205 This is the software module diagram of a typical RTOS/NSCE integration example.
227 - NSID Manager: If NSPE RTOS manages the NSID, then this module is used by the
|
| /trusted-firmware-m-latest/docs/configuration/profiles/ |
| D | tfm_profile_medium.rst | 201 The details of configurations will be covered in each module in
351 module.
|
| D | tfm_profile_small.rst | 300 The details of configurations will be covered in each module in
410 module.
|
| /trusted-firmware-m-latest/cmake/ |
| D | remote_library.cmake | 222 # [in] GIT_REPOSITORY, GIT_TAG, ... - see https://cmake.org/cmake/help/latest/module/ExternalPr…
|
| /trusted-firmware-m-latest/docs/design_docs/ |
| D | tfm_physical_attack_mitigation.rst | 551 - SAU: The main module in the CPU to determine the security settings of
553 - :term:`MPC`: External module from the CPU point of view. It protects the
557 - :term:`PPC`: External module from the CPU
|
| /trusted-firmware-m-latest/docs/design_docs/software/ |
| D | hardware_abstraction_layer.rst | 108 tfm_hal_[module].[h/c]
160 Status code to indicate that the module is not initialed.
|
