Home
last modified time | relevance | path

Searched refs:lengths (Results 1 – 7 of 7) sorted by relevance

/Zephyr-latest/tests/drivers/build_all/display/
Dapp.overlay317 chain-lengths = <256>, <256>;
/Zephyr-latest/drivers/bluetooth/hci/
DKconfig.infineon199 # Change size of command lengths. It for vendor commands related to
/Zephyr-latest/scripts/dts/python-devicetree/tests/
Dtest.dts403 // Use different data lengths for source and
/Zephyr-latest/doc/build/dts/
Dapi-usage.rst207 You can use :c:macro:`DT_PROP_LEN()` to get logical array lengths in number of
229 You **cannot** read register block addresses and lengths with ``DT_PROP(node,
/Zephyr-latest/subsys/bluetooth/controller/hci/
Dhci.c177 uint8_t lengths[CONFIG_BT_CTLR_MESH_SF_PATTERNS]; member
5557 f->lengths[i] = cmd->patterns[i].pattern_len;
5558 memcpy(f->patterns[i], cmd->patterns[i].pattern, f->lengths[i]);
6518 if (len >= f->lengths[i] &&
6519 !memcmp(data, f->patterns[i], f->lengths[i])) {
/Zephyr-latest/doc/releases/
Drelease-notes-2.4.rst955 * :github:`28317` - Asymmetric nrfx spi_transceive tx/rx lengths outputs error
Drelease-notes-2.5.rst1160 * :github:`31206` - coap.c : encoding of options with lengths larger than 268 is not proper