Searched refs:tid (Results 1 – 4 of 4) sorted by relevance
| /trusted-firmware-m-3.7.0/secure_fw/spm/ns_client_ext/ |
| D | tfm_ns_client_ext.c | 19 #define MAKE_NS_CLIENT_TOKEN(tid, gid, idx) \ argument
20 (uint32_t)((((uint32_t)tid & 0xff) \
72 uint8_t tid; in tfm_nsce_release_ctx() local
85 tid = NS_CLIENT_TOKEN_TO_TID(token); in tfm_nsce_release_ctx()
88 if (!release_ns_ctx(gid, tid, ctx_idx)) { in tfm_nsce_release_ctx()
100 uint8_t tid; in tfm_nsce_load_ctx() local
118 tid = NS_CLIENT_TOKEN_TO_TID(token); in tfm_nsce_load_ctx()
121 if (!load_ns_ctx(gid, tid, nsid, ctx_idx)) { in tfm_nsce_load_ctx()
133 uint8_t tid; in tfm_nsce_save_ctx() local
146 tid = NS_CLIENT_TOKEN_TO_TID(token); in tfm_nsce_save_ctx()
[all …]
|
| D | tfm_ns_ctx.c | 90 bool release_ns_ctx(uint8_t gid, uint8_t tid, uint8_t idx) in release_ns_ctx() argument
111 if (ns_ctx_data[idx].tid == tid) { in release_ns_ctx()
138 bool load_ns_ctx(uint8_t gid, uint8_t tid, int32_t nsid, uint8_t idx) in load_ns_ctx() argument
153 ns_ctx_data[idx].tid = tid; in load_ns_ctx()
160 bool save_ns_ctx(uint8_t gid, uint8_t tid, uint8_t idx) in save_ns_ctx() argument
171 || (ns_ctx_data[idx].tid != tid) in save_ns_ctx()
|
| D | tfm_ns_ctx.h | 22 uint8_t tid; /* Thread ID. Used to identify threads in same group */ member
44 bool release_ns_ctx(uint8_t gid, uint8_t tid, uint8_t idx);
54 bool load_ns_ctx(uint8_t gid, uint8_t tid, int32_t nsid, uint8_t idx);
63 bool save_ns_ctx(uint8_t gid, uint8_t tid, uint8_t idx);
|
| /trusted-firmware-m-3.7.0/docs/integration_guide/ |
| D | non-secure_client_extension_integration_guide.rst | 63 To support this flexibility, a group ID (gid) and a thread ID (tid) are
67 The gid and tid are specified by NSPE RTOS via NSCE interface.
101 `tid` are the input paramemters. A token will be returned to the NSPE if TF-M
104 It is the responsibility of NSPE RTOS to assign gid and tid for each NS client.
159 - Manage the assignment for `gid`, `tid` and NSID.
185 `tfm_nsce_save_ctx()` for switching the NSID for the same task (same tid and
241 - `tid`: It is a `uint8_t` value (valid range is 0 - 255). Thread ID is used to
242 identify a NS client within a given group. `tid` has no special meaning for
243 TF-M. So, usually the kernel only needs to ensure a NS task has a unique `tid`
246 - `gid` and `tid` management: It is the responsibility of NSPE RTOS to manage
[all …]
|
