Home
last modified time | relevance | path

Searched full:upwards (Results 1 – 10 of 10) sorted by relevance

/Zephyr-latest/tests/lib/heap/
Dtestcase.yaml2 # is very slow for CPU-bound tests like this, taking upwards of 10
/Zephyr-latest/dts/bindings/display/
Dsitronix,st7796s.yaml65 VCOM control setting. Value starts at 0.300V, and moves upwards in
/Zephyr-latest/doc/kernel/data_structures/
Drbtree.rst106 "upwards" from a node as well. It is very common for red/black trees
/Zephyr-latest/include/zephyr/drivers/
Dcounter.h606 * - When counting upwards (see @ref COUNTER_CONFIG_INFO_COUNT_UP) the given
614 * - counting upwards, now = 4950, top value = 5000, guard period = 100:
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.ll_sw_split257 forward invalid SDUs through HCI upwards.
/Zephyr-latest/subsys/bluetooth/controller/ll_sw/
Dull_iso.c1695 /* Let ISO PDU start its long journey upwards */ in iso_rx_demux()
/Zephyr-latest/scripts/dts/python-devicetree/src/devicetree/
Dedtlib.py974 by searching upwards for a parent node whose binding has a 'bus:' key,
/Zephyr-latest/tests/lib/devicetree/api/src/
Dmain.c2351 /* When traversing upwards, there are no fixed attributes and labels */ in ZTEST()
/Zephyr-latest/doc/releases/
Drelease-notes-3.3.rst3041 * :github:`53579` - add_compile_definitions does not "propagate upwards" as supposed to when using …
/Zephyr-latest/subsys/bluetooth/controller/hci/
Dhci.c8607 * @param net_buf[out] Upwards-going HCI buffer to fill