| /trusted-firmware-m-3.7.0/secure_fw/spm/core/ |
| D | rom_loader.c | 137 struct service_t *services; in load_services_assuredly() local
152 services = tfm_allocate_service_assuredly(p_ptldinf->nservices); in load_services_assuredly()
153 for (i = 0; i < p_ptldinf->nservices && services; i++) { in load_services_assuredly()
154 services[i].p_ldinf = &p_servldinf[i]; in load_services_assuredly()
155 services[i].partition = p_partition; in load_services_assuredly()
156 services[i].next = NULL; in load_services_assuredly()
176 stateless_services_ref_tbl[hidx] = &services[i]; in load_services_assuredly()
179 UNI_LIST_INSERT_AFTER(services_listhead, &services[i], next); in load_services_assuredly()
|
| /trusted-firmware-m-3.7.0/docs/design_docs/services/ |
| D | stateless_rot_service.rst | 16 services.
54 Since connection-based services and stateless services share the same PSA API
60 The index is used for organizing stateless services in manifest tool and
68 header files required by partition and services. For example, the generated
88 This chapter describes the changes in programming API for stateless services.
147 There are particular services that do not need sessions. The access to the
148 service is a one-shot connection. These services provide standalone operations
151 caller. Such services are recommended to be implemented as stateless, to provide
155 state or non-volatile resources while stateless services do not need them.
160 TF-M native services are used widely. They only need standalone operations and
[all …]
|
| D | tfm_uniform_secure_service_signature.rst | 34 parameters, and there is no need for the secure services to make these checks
42 The signature for such secure services would look like this:
60 secure service veneers would not apply to secure services using the uniform
108 Note that the proposal is for the two types of services (those with proprietary
|
| D | secure_partition_manager.rst | 28 Secure services (aka `Service`) is the component providing secure
30 acts as a client when it is accessing its depending services.
34 - Contains services with the same purpose.
39 usage. Clients access services by `SID` or `Handle` through FF-M `Client API`.
100 `IPC model implementation` can handle access to the services in the `SFN`
121 services in one step, an `NSPE` client needs to cross the secure boundaries
150 - These components can provide services: SFN Partition, IPC partition, and
151 built-in services. A built-in service is built up with SPM together.
152 - All partition services must be accessed by `Client API`.
154 - Built-in services are strongly recommended to be accessed by `Client API`.
[all …]
|
| /trusted-firmware-m-3.7.0/platform/ext/target/lairdconnectivity/bl5340_dvk_cpuapp/ |
| D | CMakeLists.txt | 23 …$<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/services/src/tfm_platform_system.c>
30 services/include
48 install(FILES services/include/tfm_ioctl_api.h
|
| /trusted-firmware-m-3.7.0/platform/ext/target/lairdconnectivity/common/core/ |
| D | CMakeLists.txt | 64 ${NRF_FOLDER_PATH}/services/include
85 ${NRF_FOLDER_PATH}/services/src/tfm_platform_hal_ioctl.c
86 ${NRF_FOLDER_PATH}/services/src/tfm_ioctl_core_s_api.c
91 ${NRF_FOLDER_PATH}/services/src/tfm_ioctl_core_ns_api.c
124 ${NRF_FOLDER_PATH}/services/include
173 install(FILES ${NRF_FOLDER_PATH}/services/include/tfm_ioctl_core_api.h
176 install(FILES ${NRF_FOLDER_PATH}/services/src/tfm_ioctl_core_ns_api.c
|
| /trusted-firmware-m-3.7.0/platform/ext/target/nordic_nrf/nrf5340dk_nrf5340_cpuapp/ |
| D | CMakeLists.txt | 22 …$<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/services/src/tfm_platform_system.c>
29 services/include
55 install(FILES services/include/tfm_ioctl_api.h
|
| /trusted-firmware-m-3.7.0/platform/ext/target/arm/musca_s1/ns/ |
| D | CMakeLists.txt | 22 $<$<BOOL:${PLATFORM_GPLED_ENABLED}>:services/src/tfm_ioctl_ns_api.c>
23 $<$<BOOL:${PLATFORM_GPLED_ENABLED}>:services/src/tfm_gpled_api.c>
36 $<$<BOOL:${PLATFORM_GPLED_ENABLED}>:services/include>
|
| /trusted-firmware-m-3.7.0/platform/ext/target/nordic_nrf/nrf9160dk_nrf9160/ |
| D | CMakeLists.txt | 22 …$<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/services/src/tfm_platform_system.c>
29 services/include
60 install(FILES services/include/tfm_ioctl_api.h
|
| /trusted-firmware-m-3.7.0/platform/ext/target/nordic_nrf/nrf9161dk_nrf9161/ |
| D | CMakeLists.txt | 20 …$<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/services/src/tfm_platform_system.c>
27 services/include
58 install(FILES services/include/tfm_ioctl_api.h
|
| /trusted-firmware-m-3.7.0/interface/include/psa_manifest/ |
| D | sid.h.template | 18 {% if partition.manifest.services %}
20 {% for service in partition.manifest.services %}
|
| /trusted-firmware-m-3.7.0/platform/ext/target/nordic_nrf/common/core/ |
| D | CMakeLists.txt | 74 services/include
121 services/src/tfm_platform_hal_ioctl.c
122 services/src/tfm_ioctl_core_s_api.c
181 install(FILES services/include/tfm_ioctl_core_api.h
184 install(FILES services/src/tfm_ioctl_core_ns_api.c
246 services
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/source_structure/ |
| D | source_structure.rst | 79 partitions Default services and SPRTL
90 services and platforms. Avoid putting private headers, not referenced by
95 This folder contains default services implemented as partitions and runtime
108 Here `partition_x` and `partition_y` are examples of RoT services without
114 services complied with PSA FF-M.
|
| /trusted-firmware-m-3.7.0/secure_fw/spm/ |
| D | Kconfig.comp | 13 int "Maximal number of handling secure services"
16 The maximal number of secure services that are connected or requested at
|
| /trusted-firmware-m-3.7.0/docs/ |
| D | glossary.rst | 9 `PSA term`_. The security domain in which additional security services
31 OS using services provided by TF-M.
53 A logical container for secure services.
80 One of PSA services provided by TF-M.
84 One of PSA services provided by TF-M.
|
| /trusted-firmware-m-3.7.0/tools/templates/ |
| D | manifestfilename.template | 25 {% if manifest.services %}
26 {% for service in manifest.services %}
|
| /trusted-firmware-m-3.7.0/docs/design_docs/software/ |
| D | tfm_code_generation_with_jinja2.rst | 64 Below code snippet enumerates services in Secure Partitions:
69 {% if partition.manifest.services %}
70 {% for service in partition.manifest.services %}
|
| /trusted-firmware-m-3.7.0/docs/introduction/ |
| D | readme.rst | 23 Firmware Update and Attestation secure services
27 to only include the required secure services and features. Project provides
30 be configured to include required services and features as described in the
40 utilize these secure services with a standardized set of PSA Functional APIs.
41 Applications running on Cortex-M devices can leverage TF-M services to ensure
42 secure connection with edge gateways and IoT cloud services. It also protects
|
| /trusted-firmware-m-3.7.0/docs/design_docs/ |
| D | index.rst | 9 Secure Services <services/index>
|
| /trusted-firmware-m-3.7.0/secure_fw/partitions/ |
| D | dir_services.dox | 13 \brief Source code for secure services.
|
| /trusted-firmware-m-3.7.0/platform/ext/target/arm/musca_s1/ |
| D | CMakeLists.txt | 54 services/include
82 …$<$<BOOL:${TFM_PARTITION_PLATFORM}>:${CMAKE_CURRENT_SOURCE_DIR}/services/src/tfm_platform_system.c>
158 services
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/services/ |
| D | tfm_platform_integration_guide.rst | 47 their dedicated HAL API functions. Additional platform-specific services can be
53 ``platform/ext/target/<SPECIFIC_TARGET_FOLDER>/services/src/tfm_platform_system.c``
106 isolation level 1. Currently the mechanism by which PSA-RoT services should
|
| /trusted-firmware-m-3.7.0/docs/doxygen/ |
| D | mainpage.dox | 13 This document gives a reference for the TF-M core and services. This guide does
|
| /trusted-firmware-m-3.7.0/docs/security/security_advisories/ |
| D | profile_small_key_id_encoding_vulnerability.rst | 71 Analysis of RoT services in Profile Small
76 services in Profile Small.
119 Default Profile Small RoT services don't initially call Crypto key derivation or
122 According to the analysis of RoT services above, device HUK can be accessed by
134 Impact on vendor RoT services
|
| /trusted-firmware-m-3.7.0/docs/configuration/ |
| D | index.rst | 18 a user's needs. A user can select the desired set of services and fine-tune
50 Starting from the base, users can enable required services and features using several
67 *base configuration* a user can enable necessary services and options.
69 This is new in v1.7.0 and it covers only SPM and PSA services. As an output
|
