Home
last modified time | relevance | path

Searched refs:miss (Results 1 – 12 of 12) sorted by relevance

/Zephyr-Core-3.5.0/subsys/logging/
Dlog_cache.h35 uint32_t miss; member
89 return cache->miss; in log_cache_get_miss()
Dlog_cache.c41 cache->miss = 0; in log_cache_init()
72 cache->miss++; in log_cache_get()
/Zephyr-Core-3.5.0/tests/subsys/logging/log_cache/src/
Dmain.c65 uint32_t miss = log_cache_get_miss(cache); in cache_get() local
72 zassert_equal(miss, log_cache_get_miss(cache), "line %u\n", line); in cache_get()
75 zassert_equal(miss + 1, log_cache_get_miss(cache), "line %u\n", line); in cache_get()
/Zephyr-Core-3.5.0/subsys/net/ip/
DKconfig.mgmt65 NET_MGMT_EVENT_QUEUE_SIZE from the default in order not to miss
/Zephyr-Core-3.5.0/doc/kernel/services/
Dpolling.rst264 application will miss events. Best practice is always to reset the
267 FIFOs are more error-proof in this sense because they can't "miss"
/Zephyr-Core-3.5.0/doc/connectivity/networking/conn_mgr/
Dmain.rst135 …nt listeners after connectivity monitoring initializes, it is possible to miss this first wave of …
/Zephyr-Core-3.5.0/doc/project/
Drelease_process.rst78 general rule, if you miss submitting your code during the development phase for
/Zephyr-Core-3.5.0/doc/releases/
Drelease-notes-1.7.rst435 * ``ZEP-1768`` - samples: cases miss testcase.ini
Drelease-notes-3.0.rst1164 * :github:`40189` - k_poll infrastructure can miss "signals" in a heavily contended SMP system
Drelease-notes-1.14.rst1570 * :github:`13320` - sanitycheck miss extra_args: OVERLAY_CONFIG parameter
1679 * :github:`12615` - Network documentation might miss API documentation
Drelease-notes-2.5.rst1028 …les/scheduler/metairq_dispatch: Regression after 30916 (sched: timeout: Do not miss slice timeouts)
/Zephyr-Core-3.5.0/subsys/bluetooth/mesh/
DKconfig835 is that the node may miss out on messages intended for it