Searched refs:ordering (Results 1 – 21 of 21) sorted by relevance
| /Zephyr-latest/subsys/logging/ |
| D | Kconfig.links | 18 Dedicated buffer allows to maintain ordering of processed messages.
|
| D | Kconfig.processing | 103 latency but increases chances of maintaining correct ordering of the
|
| /Zephyr-latest/tests/subsys/rtio/rtio_api/src/ |
| D | test_rtio_api.c | 719 int32_t ordering[4] = { -1, -1, -1, -1}; in test_rtio_callback_chaining_() local
767 ordering[idx] = i; in test_rtio_callback_chaining_()
773 zassert_equal(ordering[i], i, in test_rtio_callback_chaining_()
|
| /Zephyr-latest/doc/kernel/data_structures/ |
| D | rbtree.rst | 18 Unlike a list, where position is explicit, the ordering of nodes
24 the second in the ordering desired by the tree. Note that "equal" is
|
| /Zephyr-latest/tests/kconfig/configdefault/ |
| D | Kconfig | 217 # configdefault doesn't overwrite ordering
|
| /Zephyr-latest/drivers/wifi/esp_at/ |
| D | Kconfig.esp_at | 33 bool "Scan result ordering based on RSSI"
|
| /Zephyr-latest/doc/hardware/peripherals/sensor/ |
| D | read_and_decode.rst | 44 process ordering.
|
| /Zephyr-latest/doc/build/dts/api/ |
| D | api.rst | 146 A *dependency ordering* of a devicetree is a list of its nodes, where each node
156 The Zephyr build system chooses a dependency ordering of the final devicetree
158 can be accessed using the following macros. The exact dependency ordering
|
| /Zephyr-latest/doc/services/rtio/ |
| D | index.rst | 96 a cqe being pushed into the cq. The ordering of cqe may not be the same order of
97 sqe. A chain of sqe will however ensure ordering and failure cascading.
|
| /Zephyr-latest/doc/build/sysbuild/ |
| D | images.rst | 88 Additional dependency ordering can be set here if needed, see
174 Additional dependency ordering can be set here if needed, see
|
| /Zephyr-latest/boards/st/nucleo_n657x0_q/doc/ |
| D | index.rst | 37 - Features specific to some of the boards (refer to the ordering information section
|
| /Zephyr-latest/doc/build/dts/ |
| D | troubleshooting.rst | 84 * Node dependency ordering (ordinal and path):
|
| /Zephyr-latest/doc/services/logging/ |
| D | index.rst | 634 Message ordering
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.12.rst | 195 * Fixing network management event ordering.
|
| D | release-notes-1.14.rst | 50 * :github:`28177` - gPTP gptp_priority_vector struct field ordering is wrong
1561 * :github:`13380` - sockets: ordering of send() vs. poll() when using socket API + DTLS causes a cr…
|
| D | release-notes-3.5.rst | 269 * Fixed compiler instruction re-ordering that caused assertions
|
| D | release-notes-2.5.rst | 1699 * :github:`28177` - gPTP gptp_priority_vector struct field ordering is wrong
|
| D | release-notes-2.7.rst | 1859 * :github:`32133` - Current atomics are subtly broken on AArch64 due to memory ordering
|
| D | release-notes-2.6.rst | 1621 * :github:`33464` - SYS_INIT initialize priority "2-9" ordering error
|
| D | release-notes-3.2.rst | 2565 * :github:`41880` - Strict test ordering in new ztest API
|
| D | release-notes-3.3.rst | 1088 * Fixed a bug causing incorrect ordering of the observation paths.
|
