| /trusted-firmware-m-3.4.0/secure_fw/partitions/crypto/ |
| D | crypto_key.c | 43 core->MBEDTLS_PRIVATE(policy).MBEDTLS_PRIVATE(usage) = in tfm_crypto_key_attributes_from_client()
44 client_key_attr->usage; in tfm_crypto_key_attributes_from_client()
71 client_key_attr->usage = core.MBEDTLS_PRIVATE(policy).MBEDTLS_PRIVATE(usage); in tfm_crypto_key_attributes_to_client()
|
| /trusted-firmware-m-3.4.0/platform/ext/common/template/ |
| D | crypto_keys.c | 38 psa_key_usage_t *usage) in tfm_plat_builtin_key_get_usage() argument
40 *usage = 0; in tfm_plat_builtin_key_get_usage()
45 *usage = PSA_KEY_USAGE_DERIVE; in tfm_plat_builtin_key_get_usage()
51 *usage = PSA_KEY_USAGE_SIGN_HASH; in tfm_plat_builtin_key_get_usage()
54 *usage |= PSA_KEY_USAGE_EXPORT; in tfm_plat_builtin_key_get_usage()
65 *usage = PSA_KEY_USAGE_VERIFY_HASH; in tfm_plat_builtin_key_get_usage()
|
| /trusted-firmware-m-3.4.0/config/ |
| D | cp_config_default.cmake | 8 set(CONFIG_TFM_ENABLE_FP OFF CACHE BOOL "Enable/disable FP usage")
9 …CONFIG_TFM_ENABLE_MVE OFF CACHE BOOL "Enable/disable integer MVE usage")
10 …TFM_ENABLE_MVE_FP OFF CACHE BOOL "Enable/disable floating-point MVE usage")
15 … "Make FPU and MVE operational when SPE and/or NSPE require FPU or MVE usage. This alone only e…
20 … "Make FPU and MVE operational when SPE and/or NSPE require FPU or MVE usage. This alone only e…
|
| D | tfm_build_log_config.cmake | 13 … set(CONFIG_TFM_MEMORY_USAGE_QUIET ON CACHE BOOL "Disable the memory usage report")
17 … set(CONFIG_TFM_MEMORY_USAGE_QUIET OFF CACHE BOOL "Disable the memory usage report")
|
| D | cp_check.cmake | 31 …message(FATAL_ERROR "To enable FPU usage in SPE and NSPE both, please use the compiler with '-mfix…
|
| /trusted-firmware-m-3.4.0/platform/ext/target/stm/common/scripts/ |
| D | bin2hex.py | 44 usage = '''Bin2Hex convertor utility. variable
69 print(usage)
93 print(usage)
|
| /trusted-firmware-m-3.4.0/platform/ext/target/arm/rss/common/ |
| D | crypto_keys.c | 32 psa_key_usage_t *usage) in tfm_plat_builtin_key_get_usage() argument
34 *usage = 0; in tfm_plat_builtin_key_get_usage()
41 *usage = PSA_KEY_USAGE_DERIVE; in tfm_plat_builtin_key_get_usage()
47 *usage = PSA_KEY_USAGE_SIGN_HASH; in tfm_plat_builtin_key_get_usage()
50 *usage |= PSA_KEY_USAGE_EXPORT; in tfm_plat_builtin_key_get_usage()
57 *usage = PSA_KEY_USAGE_VERIFY_HASH; in tfm_plat_builtin_key_get_usage()
68 *usage = PSA_KEY_USAGE_DERIVE; in tfm_plat_builtin_key_get_usage()
78 *usage = PSA_KEY_USAGE_VERIFY_HASH; in tfm_plat_builtin_key_get_usage()
87 *usage = PSA_KEY_USAGE_VERIFY_HASH; in tfm_plat_builtin_key_get_usage()
96 *usage = PSA_KEY_USAGE_VERIFY_HASH; in tfm_plat_builtin_key_get_usage()
|
| /trusted-firmware-m-3.4.0/lib/ext/cryptocell-312-runtime/utils/src/cc3x_boot_cert/cert_utils/ |
| D | hbk_gen_util.py | 123 def usage(): function
151 usage()
159 usage()
169 usage()
|
| /trusted-firmware-m-3.4.0/lib/ext/cryptocell-312-runtime/utils/src/cc3x_boot_cert/x509cert_utils/ |
| D | hbk_gen_util.py | 123 def usage(): function
151 usage()
159 usage()
169 usage()
|
| /trusted-firmware-m-3.4.0/secure_fw/partitions/crypto/psa_driver_api/ |
| D | tfm_builtin_key_loader.c | 95 psa_key_usage_t usage = psa_get_key_usage_flags(attr); in builtin_key_get_attributes() local
101 MBEDTLS_SVC_KEY_ID_GET_OWNER_ID(key_id), &usage); in builtin_key_get_attributes()
108 psa_set_key_usage_flags(attr, usage); in builtin_key_get_attributes()
|
| /trusted-firmware-m-3.4.0/interface/include/psa/ |
| D | crypto_client_struct.h | 38 uint32_t usage; member
|
| D | crypto_struct.h | 188 attributes->client.usage = usage_flags; in psa_set_key_usage_flags()
194 return attributes->client.usage; in psa_get_key_usage_flags()
|
| /trusted-firmware-m-3.4.0/platform/include/ |
| D | tfm_plat_crypto_keys.h | 39 psa_key_usage_t *usage);
|
| /trusted-firmware-m-3.4.0/docs/integration_guide/ |
| D | tfm_fpu_support.rst | 43 when FPU is used. Otherwise, No Coprocessor (NOCP) usage fault will be asserted
66 * ``CONFIG_TFM_ENABLE_FP`` is used to enable/disable FPU usage.
84 coprocessors CP10 and CP11 on the NS side to avoid aforementioned NOCP usage
|
| /trusted-firmware-m-3.4.0/interface/src/ |
| D | tfm_ns_interface.c.example | 53 * specific implementation and usage scenario.
|
| /trusted-firmware-m-3.4.0/lib/ext/t_cose/ |
| D | README.md | 29 of memory usage making it good for embedded implementations that
192 Stack usage is less than 1KB for signing and for encryption.
204 ### Crypto library memory usage
205 In addition to the above memory usage, the crypto library will use some stack and / or
210 it will up the memory usage a lot and may require use of malloc.
|
| /trusted-firmware-m-3.4.0/docs/technical_references/design_docs/ |
| D | source_structure.rst | 71 folder for usage. As the content of the ``vendor`` folder comes by the
96 This folder holds headers for client, services and platform integration usage.
|
| D | tfm_its_512_flash.rst | 56 - The proposed implementation will increase the RAM usage of ITS by the size
|
| D | secure_partition_manager.rst | 39 usage. Clients access services by `SID` or `Handle` through FF-M `Client API`.
554 `Floatpoint Extension` is enabled for partition usage:
561 Floatpoint usage is prohibited in SPM and background execution.
698 - An optional service API set for easier client usage, by encapsulating
|
| D | tfm_psa_inter_process_communication.rst | 63 - The memory item body for caller usage.
|
| /trusted-firmware-m-3.4.0/ |
| D | toolchain_GNUARM.cmake | 61 set(MEMORY_USAGE_FLAG LINKER:--print-memory-usage)
83 message(WARNING "Cortex-m85 is not supported by GCC. Falling back to -march usage.")
|
| /trusted-firmware-m-3.4.0/docs/configuration/profiles/ |
| D | tfm_profile_medium.rst | 66 Profile Medium with IPC model and isolation level 2 aims to support usage
112 algorithms according to actual usage scenarios and device capabilities.
131 If usage scenarios require RSA algorithm for backward compatibility and legacy
|
| D | tfm_profile_large.rst | 14 complex usage scenarios.
93 In some usage scenarios, PSA RoT can be managed by device manufacturer or other
|
| /trusted-firmware-m-3.4.0/lib/ext/cryptocell-312-runtime/codesafe/src/psa_driver_api/ |
| D | psa_driver_api_design.rst | 130 The driver interface is configurable through usage of compile time definitions.
144 algorithms in Hash and HMAC. As SHA-1 is deemed unsecure and its usage not
|
| /trusted-firmware-m-3.4.0/docs/security/threat_models/ |
| D | generic_threat_model.rst | 75 The TOE can vary in different TF-M models, RoT services and usage scenarios.
102 can be defined in an actual usage scenario and a dedicated threat model.
191 usage scenarios.
240 mitigation, in diverse TF-M models and usage scenarios.
243 threats. For the details in a specific configuration and usage scenario,
|
