| /trusted-firmware-m-3.7.0/docs/design_docs/services/ |
| D | tfm_psa_inter_process_communication.rst | 63 - The memory item body for caller usage.
134 - Block-able: Block-able API may block caller thread; Non-Block API does not
135 block caller thread.
146 or version to the caller.
163 After a message response is returned to the caller, the waiting caller gets
172 - This API blocks caller partition if there is no expected event for it. This
191 - These APIs do not take the initiative to change caller status. They process
192 data and return the processed data back to the caller.
201 not take the initiative to change caller status.
|
| D | secure_partition_runtime_library.rst | 44 These APIs access caller stack and caller provided memory only.
161 This would simplify the caller logic into this:
172 defined in RoT Service headers and the instance is allocated by API caller since
180 implemented inside the caller client, instead of putting it into SPRTL.
203 checking must happen in Core while caller is calling these interface.
348 the prototype. Heap management code is put in the SPRTL for sharing with caller
352 'instance', while for 'malloc' caller it needs a 'malloc' with one parameter
|
| D | tfm_crypto_design.rst | 61 …| | This module is in charge of providing an ID of the caller of | …
67 …| | caller view of contexts, i.e. `clients`, does not contain any | …
72 …| | ``MBEDTLS_PSA_CRYPTO_CLIENT`` option on the caller side. Note | …
|
| D | stateless_rot_service.rst | 151 caller. Such services are recommended to be implemented as stateless, to provide
|
| D | secure_partition_manager.rst | 399 - Can see the prepared caller and callee context, with exited SPM context. It
410 * Now both the caller and callee contexts are
|
| D | tfm_its_service.rst | 265 different flash device. It can use the client ID to detect when the caller is
|
| /trusted-firmware-m-3.7.0/docs/security/security_advisories/ |
| D | svc_caller_sp_fetching_vulnerability.rst | 30 When a non-secure caller calls the secure function, the execution switches the
34 handler code relies on the 'SPSEL' bit in 'EXC_RETURN' to get the caller stack
55 stack for handling the request in the NSPE caller in 'Handler mode' case.
70 caller saved registers in the context as parameters for the subsequent
75 When PSP_S is pointing to the stack bottom when this issue happens, the caller
|
| D | fwu_write_vulnerability.rst | 17 | Impact | In IPC model, the caller of ``psa_fwu_write()`` from SPE |
64 In IPC model, the caller of ``psa_fwu_write()`` from SPE or NSPE can overwrite
|
| D | profile_small_key_id_encoding_vulnerability.rst | 46 array. When a caller requests to access a key, TF-M Crypto service validates
47 the request by comparing the caller client ID with the stored key client ID.
50 key ID. When a caller requests to access a key, Mbed TLS validates the
51 request by comparing the caller client ID with the key client ID stored in
|
| /trusted-firmware-m-3.7.0/interface/include/psa/ |
| D | initial_attestation.h.in | 31 * or the hash of some combined data : nonce + attested data by caller.
53 * - Challenge: Input object from caller. Can be a single nonce from server
55 * freshness to reports and the caller has responsibility to
108 * represents non-secure caller, positive numbers represents
183 * It just returns with the size of the IAT token. It can be used if the caller
|
| /trusted-firmware-m-3.7.0/secure_fw/spm/core/ |
| D | backend_ipc.c | 409 struct partition_t *caller = GET_CURRENT_COMPONENT(); in backend_abi_entering_spm() local
425 if ((caller->ctx_ctrl.sp <= SPM_THREAD_CONTEXT->sp_limit) || in backend_abi_entering_spm()
426 (caller->ctx_ctrl.sp > SPM_THREAD_CONTEXT->sp_base)) { in backend_abi_entering_spm()
|
| /trusted-firmware-m-3.7.0/docs/platform/arm/rse/ |
| D | rse_comms.rst | 46 The ``client_id`` can be used by the caller to identify different clients at the
81 in io_size. The caller does not need to pad the payload to the maximum size. The
115 host system memory. It is the caller's responsibility to write the invec data to
|
| /trusted-firmware-m-3.7.0/lib/ext/t_cose/ |
| D | README.md | 27 there is no recursion. The caller supplies the memory to hold the
28 completed COSE_Sign1 and encode/decode contexts so caller has full control
198 however the caller wishes, even in ROM, since it is only read.
202 allocated however the caller wishes.
|
| /trusted-firmware-m-3.7.0/docs/design_docs/dual-cpu/ |
| D | mailbox_ns_agent_update.rst | 44 - SPM treats FF-M Client API caller's ID as the client ID. While the mailbox NS
48 - FF-M Client API blocks caller before the call is replied; while the
89 mailbox API is calling Client API. The standard API treats the caller as the
|
| D | communication_prototype_between_nspe_and_spe_in_dual_core_systems.rst | 530 | ``PSA_VERSION_NONE`` | The RoT Service is not implemented, or the caller is |
574 | | or the caller is not permitted to access the |
|
| D | mailbox_design_on_dual_core_system.rst | 291 proper mechanism(s) to keep current caller waiting for PSA Client result or an
539 ``MAILBOX_NO_PERMS`` is a return value from mailbox function if the caller
1258 The function caller should be blocked until a PSA Client call request is
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/services/ |
| D | tfm_attestation_integration_guide.rst | 39 - **Auth challenge**: Input object from caller. Can be a single nonce from
41 freshness to report and the caller has responsibility to arrange
83 caller, positive numbers represents secure callers, zero is invalid.
234 The caller must allocate a large enough buffer, where the token is going to be
277 - ``attest_get_caller_client_id()``: Retrieves the ID of the caller thread.
|
| D | tfm_secure_partition_addition.rst | 764 the caller client ID anymore.
767 validate the secure caller anymore.
|
| /trusted-firmware-m-3.7.0/docs/design_docs/booting/ |
| D | secure_boot_hw_key_integration.rst | 137 not directly accessible, therefore a buffer is allocated by the caller to store
|
| /trusted-firmware-m-3.7.0/docs/design_docs/ |
| D | tfm_builtin_keys.rst | 183 The HUK is used for key derivation by any secure partition or NS caller that
187 partition / NS caller, it must be ensured that no service that utilises HUK
|
| D | ff_isolation.rst | 403 caller of the PSA APIs is permitted to access some memory ranges.
|
| /trusted-firmware-m-3.7.0/docs/design_docs/software/ |
| D | tfm_cooperative_scheduling_rules.rst | 175 SPE request corresponding to currently active NSPE caller is not yet completed
|
| /trusted-firmware-m-3.7.0/docs/configuration/profiles/ |
| D | tfm_profile_small.rst | 203 Copying data to it from the caller can align all write requests to the flash
|
| /trusted-firmware-m-3.7.0/docs/security/threat_models/ |
| D | generic_threat_model.rst | 925 | | besides secure FP context in FP caller registers, FP |
1009 | | context in FP caller registers, FP context in callee |
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/platform/ |
| D | porting_tfm_to_a_new_hardware.rst | 713 It should return the result for callers and the SPM will then return it to the caller.
|
