Searched full:zli (Results 1 – 13 of 13) sorted by relevance
| /Zephyr-Core-3.7.0/tests/drivers/counter/counter_basic_api/boards/ |
| D | nrf52840dk_nrf52840_zli.overlay | 2 zli;
6 zli;
10 zli;
14 zli;
18 zli;
22 zli;
|
| /Zephyr-Core-3.7.0/samples/bluetooth/hci_uart/dts/arm/nordic/ |
| D | override.dtsi | 3 * levels for Exceptions and ZLI (if enabled).
5 * support for ZLI on Cortex-M0.
|
| /Zephyr-Core-3.7.0/dts/bindings/timer/ |
| D | nordic,nrf-timer.yaml | 42 zli:
44 description: Enable event handler in the ZLI (Zero latency interrupt) context
|
| /Zephyr-Core-3.7.0/dts/bindings/rtc/ |
| D | nordic,nrf-rtc.yaml | 37 zli:
39 description: Enable event handler in the ZLI (Zero latency interrupt) context
|
| /Zephyr-Core-3.7.0/samples/bluetooth/hci_ipc/dts/arm/nordic/ |
| D | override.dtsi | 3 * levels for Exceptions and ZLI (if enabled).
|
| /Zephyr-Core-3.7.0/tests/drivers/watchdog/wdt_basic_api/boards/ |
| D | nrf52840dk_nrf52840_counter.overlay | 10 zli;
|
| /Zephyr-Core-3.7.0/subsys/testsuite/include/zephyr/ |
| D | busy_sim.h | 28 * @param cb Callback called from the context of the busy simulator timeout. If ZLI interrupt
|
| /Zephyr-Core-3.7.0/drivers/watchdog/ |
| D | Kconfig | 43 zero latency interrupts (ZLI) then expiration callback can be called from
|
| /Zephyr-Core-3.7.0/include/zephyr/arch/arm/ |
| D | irq.h | 119 "ZLI interrupt registered but feature is disabled"); \
128 "ZLI interrupt registered but feature is disabled"); \
|
| /Zephyr-Core-3.7.0/drivers/counter/ |
| D | counter_nrfx_timer.c | 411 COND_CODE_1(DT_INST_PROP(idx, zli), \
432 COND_CODE_1(DT_INST_PROP(idx, zli), ( \
|
| D | counter_nrfx_rtc.c | 694 COND_CODE_1(DT_INST_PROP(idx, zli), \
707 COND_CODE_1(DT_INST_PROP(idx, zli), ( \
|
| /Zephyr-Core-3.7.0/doc/hardware/arch/ |
| D | arm_cortex_m.rst | 257 interrupt. If the ZLI feature is enabled in Mainline Cortex-M builds (see
324 locking. To use the ZLI feature :kconfig:option:`CONFIG_ZERO_LATENCY_IRQS` needs to be enabled.
329 Note, however, that since ZLI ISRs will run at a priority level higher than the kernel
330 exceptions they **cannot use** any kernel functionality. Additionally, since the ZLI
332 in ZLI ISRs will escalate to HardFault and will not be handled in the same way as regular
|
| /Zephyr-Core-3.7.0/tests/drivers/timer/nrf_rtc_timer/src/ |
| D | main.c | 295 * against fixed zli interrupt pattern. in ZTEST()
|
