Home
last modified time | relevance | path

Searched refs:outs (Results 1 – 4 of 4) sorted by relevance

/Zephyr-Core-3.7.0/tests/drivers/uart/uart_pm/src/
Dmain.c18 char outs[] = "abc"; in polling_verify() local
25 for (int i = 0; i < ARRAY_SIZE(outs); i++) { in polling_verify()
26 uart_poll_out(dev, outs[i]); in polling_verify()
35 for (int i = 0; i < ARRAY_SIZE(outs); i++) { in polling_verify()
36 uart_poll_out(dev, outs[i]); in polling_verify()
45 zassert_equal(c, outs[i]); in polling_verify()
/Zephyr-Core-3.7.0/lib/os/
Dcbprintf_complete.c1348 static int outs(cbprintf_cb __out, in outs() function
1399 int rc = outs(out, ctx, (_sp), (_ep)); \ in z_cbvprintf_impl()
/Zephyr-Core-3.7.0/kernel/
DKconfig.vm127 bool "Allow interrupts during page-ins/outs"
/Zephyr-Core-3.7.0/doc/hardware/porting/
Darch.rst541 Such carve-outs will always be tracked in ``thread.stack_info.start``.
646 Guard carve-outs for kernel stacks are uncommon and should be avoided if
670 be able to be placed before it, with support for carve-outs if necessary.