Home
last modified time | relevance | path

Searched refs:interface (Results 1 – 25 of 93) sorted by relevance

1234

/trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/Driver/DriverTemplates/
DDriver_WiFi.c69 static int32_t ARM_WiFi_SetOption (uint32_t interface, uint32_t option, const void *data, uint32_t … in ARM_WiFi_SetOption() argument
73 static int32_t ARM_WiFi_GetOption (uint32_t interface, uint32_t option, void *data, uint32_t *len) { in ARM_WiFi_GetOption() argument
80 static int32_t ARM_WiFi_Activate (uint32_t interface, const ARM_WIFI_CONFIG_t *config) { in ARM_WiFi_Activate() argument
84 static int32_t ARM_WiFi_Deactivate (uint32_t interface) { in ARM_WiFi_Deactivate() argument
96 static int32_t ARM_WiFi_BypassControl (uint32_t interface, uint32_t mode) { in ARM_WiFi_BypassControl() argument
100 static int32_t ARM_WiFi_EthSendFrame (uint32_t interface, const uint8_t *frame, uint32_t len){ in ARM_WiFi_EthSendFrame() argument
104 static int32_t ARM_WiFi_EthReadFrame (uint32_t interface, uint8_t *frame, uint32_t len){ in ARM_WiFi_EthReadFrame() argument
108 static uint32_t ARM_WiFi_EthGetRxFrameSize (uint32_t interface){ in ARM_WiFi_EthGetRxFrameSize() argument
DDriver_ETH_PHY.c62 static int32_t ARM_ETH_PHY_SetInterface(uint32_t interface) in ARM_ETH_PHY_SetInterface() argument
64 switch (interface) in ARM_ETH_PHY_SetInterface()
/trusted-firmware-m-latest/platform/ext/cmsis/CMSIS/Driver/Include/
DDriver_WiFi.h632 …int32_t (*SetOption) (uint32_t interface, uint32_t option, const v…
633 …int32_t (*GetOption) (uint32_t interface, uint32_t option, v…
635 …int32_t (*Activate) (uint32_t interface, const ARM_WIFI_CONFIG_t …
636 int32_t (*Deactivate) (uint32_t interface);
639 int32_t (*BypassControl) (uint32_t interface, uint32_t mode);
640 …int32_t (*EthSendFrame) (uint32_t interface, const uint8_t *frame, ui…
641 …int32_t (*EthReadFrame) (uint32_t interface, uint8_t *frame, ui…
642 uint32_t (*EthGetRxFrameSize) (uint32_t interface);
DDriver_ETH_PHY.h133 …int32_t (*SetInterface) (uint32_t interface); ///< Pointer to \ref ARM_ETH_P…
/trusted-firmware-m-latest/interface/
DCMakeLists.txt15 ${CMAKE_BINARY_DIR}/generated/interface/include/psa/framework_feature.h
18 ###################### PSA interface (header only) #############################
25 $<BUILD_INTERFACE:${CMAKE_BINARY_DIR}/generated/interface/include>
61 ${CMAKE_BINARY_DIR}/generated/interface/include/tfm_mailbox_config.h
/trusted-firmware-m-latest/docs/integration_guide/services/
Dtfm_crypto_integration_guide.rst22 - An interface layer that exposes the PSA Crypto API to either NS or S entities
23 and is implemented in ``interface/src/tfm_crypto_api.c``. The interface is
28 dispatcher that at runtime receives the requests from the interface and
44 subsystem for key storage and retrieval, and, in case, the interface to the
46 cryptoprocessor driver interface specification [2]_. For this reason, it must
55 The PSA interfaces for the Crypto service are located in ``interface/include``.
65 description of the PSA API interface, please refer to the comments in the
87 - ``crypto_library.c`` : Library abstractions to interface the dispatchers
99 - ``tfm_crypto_api.c`` : This module is contained in ``interface/src`` and
100 implements the PSA Crypto API client interface exposed to both S/NS clients.
[all …]
Dtfm_its_integration_guide.rst90 ``interface/include/psa``.
106 ``interface/include/psa/storage_common.h``,
107 ``interface/include/psa/internal_trusted_storage.h``, and
108 ``interface/include/tfm_its_defs.h``
149 The ITS filesystem flash interface is defined by ``struct its_flash_fs_ops_t``
152 Implementations of the ITS filesystem flash interface for different types of
156 interface implementation for the target, and abstracts the allocation of
159 - ``flash/its_flash_nand.c`` - Implements the ITS flash interface for a NAND
160 flash device, on top of the CMSIS flash interface implemented by the target.
165 - ``flash/its_flash_nor.c`` - Implements the ITS flash interface for a NOR flash
[all …]
/trusted-firmware-m-latest/secure_fw/partitions/initial_attestation/
DCMakeLists.txt14 configure_file(${CMAKE_SOURCE_DIR}/interface/include/psa/initial_attestation.h.in
15 ${CMAKE_BINARY_DIR}/generated/interface/include/psa/initial_attestation.h)
78 ${CMAKE_BINARY_DIR}/generated/interface/include/
/trusted-firmware-m-latest/platform/ext/accelerator/
DCMakeLists.txt31 interface
45 interface
/trusted-firmware-m-latest/docs/integration_guide/
Dindex.rst56 The files needed for the interface with TF-M are exported at the
57 ``<install_dir>/interface`` path. The NS side is only allowed to call
60 TF-M interface header files are exported in ``<install_dir>/interface/include``
62 in the file ``<install_dir>/interface/include/psa/protected_storage.h``.
65 ``<install_dir>/interface/src``.
71 ``interface\src\os_wrapper\tfm_ns_interface_rtos.c``) uses mutex to provide
73 ``interface/include/os_wrapper/mutex.h`` are expected to be provided by NS RTOS.
77 ``interface\src\os_wrapper\tfm_ns_interface_bare_metal.c``) does not
79 interface.
84 under folder ``interface/src/multi_core``.
/trusted-firmware-m-latest/secure_fw/partitions/firmware_update/
DCMakeLists.txt56 configure_file(${CMAKE_SOURCE_DIR}/interface/include/psa/fwu_config.h.in
57 ${CMAKE_BINARY_DIR}/generated/interface/include/psa/fwu_config.h
59 set(FWU_DEVICE_CONFIG_FILE "${CMAKE_BINARY_DIR}/generated/interface/include/psa/fwu_config.h")
/trusted-firmware-m-latest/platform/ext/accelerator/cc312/
DCMakeLists.txt133 # Control the enablement of the legacy CC-312 driver interface or the PSA
134 # driver interface. Default value is for the legacy interface
136 "This variable controls whether the legacy driver interface is used for CC-312." ON)
145 … "The CC-312 legacy driver interface fallback is forced to ${CC312_LEGACY_DRIVER_API_ENABLED}. \
149 …_FLOAT_ABI: ${CONFIG_TFM_FLOAT_ABI}) for the PSA Cryptoprocessor driver interface due to flash mem…
159 … "The CC-312 legacy driver interface fallback is forced to ${CC312_LEGACY_DRIVER_API_ENABLED}. \
163 …TFM_PLATFORM: ${TFM_PLATFORM}) for the PSA Cryptoprocessor driver interface due to flash memory co…
/trusted-firmware-m-latest/lib/ext/cryptocell-312-runtime/codesafe/src/psa_driver_api/
Dpsa_driver_api_design.rst5 This document describes the high level design of the driver interface to the
6 CC-312 Cryptoprocessor based on PSA interfaces. The driver interface is named
12 …rface <https://github.com/ARMmbed/mbedtls/blob/development/docs/proposed/psa-driver-interface.md>`_
17 The PSA Cryptoprocessor Driver interface describes a way to uniformly interface
26 Implementations with more complex requirements can extend the driver interface
37 Overall, the driver is a high-level interface between the PSA Crypto driver
57 as well. It's worth to note that when the driver interface is enabled in the
130 The driver interface is configurable through usage of compile time definitions.
132 is not strictly a configuration option of the driver interface but it enables
143 * ``CC3XX_CONFIG_SUPPORT_SHA1``: Enable the driver interface support for SHA-1
[all …]
DCMakeLists.txt16 # PSA Cryptoprocessor Unified Driver interface entry point sources
/trusted-firmware-m-latest/docs/building/
Drun_tfm_examples_on_arm_platforms.rst144 Running Test Suite PS secure interface tests (TFM_PS_TEST_2XXX)...
147 Description: 'Create interface'
150 Description: 'Get handle interface (DEPRECATED)'
158 Description: 'Write interface'
161 Description: 'Read interface'
200 Running Test Suite PS secure interface tests (TFM_PS_TEST_2XXX)...
203 Description: 'Create interface'
206 Description: 'Get handle interface (DEPRECATED)'
214 Description: 'Write interface'
217 Description: 'Read interface'
[all …]
/trusted-firmware-m-latest/docs/security/security_advisories/
Dcc3xx_partial_tag_compare_on_chacha20_poly1305.rst6 | | PSA driver API interface in CryptoCell enabled platforms |
85 Unified Driver interface is located into the ``psa_driver_api`` directory in
92 API interface layer but rely on the legacy interface. To enable the PSA Driver
93 interface the following TF-M build option during CMake config must be be set
99 When the PSA Driver API interface is used and is not configured to rely on the
144 .. [3] PSA Unified Driver interface: \ https://github.com/Mbed-TLS/mbedtls/blob/development/docs/pr…
Ddebug_log_vulnerability.rst18 | | via stdio interface if TFM_SP_LOG_RAW_ENABLED is set |
29 uses a SVC call to print logging messages on the stdio output interface.
/trusted-firmware-m-latest/cmake/
Dinstall.cmake26 install(FILES ${CMAKE_BINARY_DIR}/generated/interface/include/psa_manifest/sid.h
29 install(FILES ${CMAKE_BINARY_DIR}/generated/interface/include/config_impl.h
46 install(FILES ${CMAKE_BINARY_DIR}/generated/interface/include/psa/framework_feature.h
54 ${CMAKE_BINARY_DIR}/generated/interface/include/tfm_mailbox_config.h
106 install(FILES ${CMAKE_BINARY_DIR}/generated/interface/include/psa/initial_attestation.h
120 ${CMAKE_BINARY_DIR}/generated/interface/include/psa/fwu_config.h
287 $<INSTALL_INTERFACE:interface/include>
Dspe-CMakeLists.cmake21 set(INTERFACE_SRC_DIR ${CMAKE_CURRENT_LIST_DIR}/interface/src)
22 set(INTERFACE_INC_DIR ${CMAKE_CURRENT_LIST_DIR}/interface/include)
36 # Include interface headers exported by TF-M
53 ${CMAKE_CURRENT_SOURCE_DIR}/interface/lib/s_veneers.o
/trusted-firmware-m-latest/bl1/bl1_2/lib/
DCMakeLists.txt12 ./interface
/trusted-firmware-m-latest/docs/releases/
D1.8.1.rst9 on the PSA driver API interface in CryptoCell enabled
/trusted-firmware-m-latest/bl1/bl1_1/lib/
DCMakeLists.txt19 interface
/trusted-firmware-m-latest/docs/design_docs/services/
Dtfm_crypto_design.rst43 …| Client API interface | This module exports the PSA Crypto API to be callable from the| ``…
85 …| Backend library abstraction | This module contains several APIs to abstract the interface | ``…
99 … | The ``tfm_crypto_api.h`` header contains public service APIs, | ``interface/include/tfm_cryp…
100 …| | which expose each module's interface. The header available in | …
101 …| | the interface, ``tfm_crypto_defs.h``, contains types and | …
102 …| | definitions to build the client interface of the service, i.e.| …
123 …| | components (i.e. other partitions or NS interface). | …
165 + Cortex-M systems, by an SPM mediated interface, e.g. partition to partition
171 the library interface and the ``tfm_crypto_api.c`` interface. When there is a
208 must interface with it to store, retrieve or use them for crypto tasks, etc.
[all …]
Dtfm_uniform_secure_service_signature.rst10 Declaring secure service interface
22 ``interface/include/<service_name>_veneers.h`` file with the veneer declarations
97 ``interface/include/tfm_veneers.h`` and ``secure_fw\ns_callable\tfm_veneers.c``
/trusted-firmware-m-latest/platform/
DCMakeLists.txt33 #====================== CMSIS stack override interface ========================#
48 #========================= Platform Common interface ==========================#
62 $<$<BOOL:${CRYPTO_HW_ACCELERATOR}>:${CMAKE_CURRENT_SOURCE_DIR}/ext/accelerator/interface>
160 … $<$<BOOL:${PLATFORM_DEFAULT_CRYPTO_KEYS}>:${CMAKE_SOURCE_DIR}/interface/include/crypto_keys>
161 ${CMAKE_BINARY_DIR}/generated/interface/include
183 … $<$<BOOL:${CRYPTO_HW_ACCELERATOR}>:${CMAKE_CURRENT_SOURCE_DIR}/ext/accelerator/interface>

1234