Home
last modified time | relevance | path

Searched refs:tfm_hal_get_ns_access_attr (Results 1 – 7 of 7) sorted by relevance

/trusted-firmware-m-latest/platform/include/
Dtfm_hal_multi_core.h68 void tfm_hal_get_ns_access_attr(const void *p, size_t s,
/trusted-firmware-m-latest/platform/ext/target/arm/corstone1000/
Dtfm_hal_multi_core.c100 void tfm_hal_get_ns_access_attr(const void *p, size_t s, in tfm_hal_get_ns_access_attr() function
/trusted-firmware-m-latest/platform/ext/target/rpi/rp2350/
Dtfm_hal_multi_core.c142 void tfm_hal_get_ns_access_attr(const void *p, size_t s, in tfm_hal_get_ns_access_attr() function
/trusted-firmware-m-latest/docs/design_docs/dual-cpu/
Dtfm_multi_core_access_check.rst84 - ``tfm_hal_get_ns_access_attr()`` retrieves non-secure access attributes of the target memory
137 tfm_hal_get_ns_access_attr(p, s, &mem_attr);
252 ``tfm_hal_get_secure_access_attr()`` and ``tfm_hal_get_ns_access_attr()`` implementations should
372 ``tfm_hal_get_ns_access_attr()``
375 ``tfm_hal_get_ns_access_attr()`` retrieves the non-secure memory protection configuration
380 void tfm_hal_get_ns_access_attr(const void *p, size_t s,
402 ``tfm_hal_get_ns_access_attr()`` execution in TF-M.
403 When the target memory region is not specified in non-secure MPU, ``tfm_hal_get_ns_access_attr()``
408 according to platform resource assignment, ``tfm_hal_get_ns_access_attr()`` can set the following
/trusted-firmware-m-latest/platform/ext/target/cypress/psoc64/
Dtfm_hal_multi_core.c138 void tfm_hal_get_ns_access_attr(const void *p, size_t s, in tfm_hal_get_ns_access_attr() function
/trusted-firmware-m-latest/secure_fw/partitions/ns_agent_mailbox/
Dtfm_multi_core_mem_check.c427 tfm_hal_get_ns_access_attr(p, s, &mem_attr); in tfm_has_access_to_region()
/trusted-firmware-m-latest/docs/integration_guide/platform/
Dporting_tfm_to_a_new_hardware.rst671 tfm_hal_get_ns_access_attr:
680 void tfm_hal_get_ns_access_attr(const void *p, size_t s, struct mem_attr_info_t *p_attr);