Searched refs:signals (Results 1 – 12 of 12) sorted by relevance
| /trusted-firmware-m-3.6.0/secure_fw/partitions/ns_agent_mailbox/ |
| D | ns_agent_mailbox.c | 30 psa_signal_t signals = 0; in ns_agent_mailbox_entry() local
42 signals = psa_wait(PSA_WAIT_ANY, PSA_BLOCK); in ns_agent_mailbox_entry()
43 if (signals & MAILBOX_SIGNAL) { in ns_agent_mailbox_entry()
47 } else if (signals & ASYNC_MSG_REPLY) { in ns_agent_mailbox_entry()
|
| /trusted-firmware-m-3.6.0/secure_fw/spm/core/ |
| D | backend_sfn.c | 160 psa_signal_t backend_wait_signals(struct partition_t *p_pt, psa_signal_t signals) in backend_wait_signals() argument
162 while (!(p_pt->signals_asserted & signals)) { in backend_wait_signals()
166 return p_pt->signals_asserted & signals; in backend_wait_signals()
|
| D | backend_ipc.c | 356 psa_signal_t backend_wait_signals(struct partition_t *p_pt, psa_signal_t signals) in backend_wait_signals() argument
367 ret = p_pt->signals_asserted & signals; in backend_wait_signals()
369 p_pt->signals_waiting = signals; in backend_wait_signals()
|
| /trusted-firmware-m-3.6.0/secure_fw/spm/include/ffm/ |
| D | backend.h | 51 psa_signal_t backend_wait_signals(struct partition_t *p_pt, psa_signal_t signals);
|
| /trusted-firmware-m-3.6.0/docs/integration_guide/ |
| D | spm_backends.rst | 15 The Secure Partition processes signals in any order, and can defer
16 responding to a message while continuing to process other signals.
|
| /trusted-firmware-m-3.6.0/docs/design_docs/dual-cpu/ |
| D | mailbox_ns_agent_update.rst | 40 ``partition``. The agent has an endless loop and waits for signals, calls FFM
98 mailbox NS agents. With this mechanism, extra signals and APIs for message
112 signals and types are also involved.
273 put in member ``rhandle``. If no 'ASYNC_MSG_REPLY' signals pending, calling
295 psa_signal_t signals;
302 signals = psa_wait(ALL, BLOCK);
304 if (signals & MAILBOX_INTERRUPT_SIGNAL) {
344 } else if (signals & ASYNC_MSG_REPLY) {
|
| D | mailbox_design_on_dual_core_system.rst | 883 | | found and wake-up signals were sent. |
|
| /trusted-firmware-m-3.6.0/docs/releases/ |
| D | 1.8.0.rst | 15 - FF-M API uses signals to drive the partition scheduling instead of controlling partition context
|
| /trusted-firmware-m-3.6.0/docs/integration_guide/services/ |
| D | tfm_secure_partition_addition.rst | 473 This function must have a loop that repeatedly waits for input signals and
483 psa_signal_t signals = 0;
490 * interrupt signals to be asserted and then handle the asserted
494 signals = psa_wait(PSA_WAIT_ANY, PSA_BLOCK);
495 if (signals & ROT_A_SIGNAL) {
|
| D | tfm_manifest_tool_user_guide.rst | 205 implementation, such as RoT Service signals and Secure Functions.
|
| /trusted-firmware-m-3.6.0/docs/platform/arm/rss/ |
| D | rss_provisioning.rst | 106 signals the lifecycle state as a hardware signal, but additionally the software
|
| /trusted-firmware-m-3.6.0/docs/design_docs/services/ |
| D | secure_partition_manager.rst | 68 There is `ONE` thread inside the partition keeps waiting for signals. SPM
271 handled by signals and messages asynchronously, hence IPC partitions can
327 specific signals.
|
