Home
last modified time | relevance | path

Searched refs:capture (Results 1 – 5 of 5) sorted by relevance

/trusted-firmware-m-3.4.0/platform/ext/target/nxp/common/Native_Driver/drivers/
Dfsl_ctimer.c449 ctimer_capture_channel_t capture, in CTIMER_SetupCapture() argument
459 << ((uint32_t)capture * 3U)); in CTIMER_SetupCapture()
460 reg |= ((uint32_t)edge) << (CTIMER_CCR_CAP0RE_SHIFT + ((uint32_t)capture * 3U)); in CTIMER_SetupCapture()
462 CTIMER_ClearStatusFlags(base, (((uint32_t)kCTIMER_Capture0Flag) << (uint32_t)capture)); in CTIMER_SetupCapture()
466 reg |= ((uint32_t)CTIMER_CCR_CAP0I_MASK) << ((uint32_t)capture * 3U); in CTIMER_SetupCapture()
Dfsl_ctimer.h343 ctimer_capture_channel_t capture,
/trusted-firmware-m-3.4.0/docs/technical_references/design_docs/
Dtfm_its_512_flash.rst63 The device's flash APIs should provide a mechanism to capture and raise
/trusted-firmware-m-3.4.0/config/
Dconfig_base.cmake56 … OFF CACHE BOOL "On fatal errors in the secure firmware, capture info about the ex…
/trusted-firmware-m-3.4.0/docs/security/threat_models/
Dgeneric_threat_model.rst668 | | mapping. SPE may fail to capture those invalid NS memory |
701 | | specific implementation to capture invalid memory address. |