Searched refs:pair (Results 51 – 75 of 87) sorted by relevance
1234
/Zephyr-latest/samples/subsys/fs/littlefs/ |
D | README.rst | 32 [00:00:00.010,559] <err> littlefs: Corrupted dir pair at 0 1
|
/Zephyr-latest/doc/services/settings/ |
D | index.rst | 14 Settings items are stored as key-value pair strings. By convention, 200 /* key-value pair was properly read.
|
/Zephyr-latest/doc/services/storage/zms/ |
D | zms.rst | 15 The key-value pair is divided into two parts: 277 Each Key-value pair needs an extra 16 bytes for ATE which makes it possible to store 11 pairs 331 For id/data pair with data <= 8 bytes, effective_size is 16 bytes 332 For id/data pair with data > 8 bytes, effective_size is 16 bytes + sizeof(data)
|
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
D | csip.rst | 138 consisting of at least two devices, e.g. a pair of earbuds.
|
D | cap.rst | 11 a pair with one or more other CAP Acceptors.
|
/Zephyr-latest/doc/kernel/data_structures/ |
D | slist.rst | 69 Internally, a :c:type:`sys_slist_t` struct is nothing more than a pair of
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | net_mgmt.rst | 53 pair of layer and code, whereas on the command part it will be a mask of
|
/Zephyr-latest/boards/renesas/mck_ra8t1/doc/ |
D | index.rst | 47 - Inverter board connector (2 pair)
|
/Zephyr-latest/doc/connectivity/bluetooth/api/ |
D | hci.txt | 824 handle pair. 886 | | the Handle_Type and Handle pair. The | 916 | | and pair formatted as a 1 octet | 947 by a pair of Handle_Type and Handle is retrieved from the controller. 1012 | | Handle_Type and Handle pair. |
|
/Zephyr-latest/doc/introduction/ |
D | index.rst | 176 configuration and runtime state. Settings items are stored as key-value pair
|
/Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
D | smp_group_1.rst | 40 This means that pair of slots is dedicated to single upgradable application. 172 | | optional when using MCUboot's serial recovery feature with one pair of |
|
/Zephyr-latest/doc/services/crypto/ |
D | psa_crypto.rst | 87 device state, to the ability to generate a key pair and prove that it
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | provisioning.rst | 100 mechanism. In this case, a new key pair will be generated by the mesh stack
|
/Zephyr-latest/doc/kernel/services/timing/ |
D | timers.rst | 188 to do useful work while ensuring that a pair of protocol operations
|
/Zephyr-latest/tests/bluetooth/tester/src/ |
D | btp_gap.c | 1190 static uint8_t pair(const void *cmd, uint16_t cmd_len, function 1798 .func = pair,
|
/Zephyr-latest/subsys/bluetooth/host/ |
D | smp.c | 4126 goto pair; in smp_security_request() 4138 goto pair; in smp_security_request() 4146 goto pair; in smp_security_request() 4150 goto pair; in smp_security_request() 4157 goto pair; in smp_security_request() 4171 pair: in smp_security_request()
|
D | Kconfig | 413 (SMP), making it possible to pair devices over LE. 667 predefined Diffie-Hellman private/public key pair is used as described 703 is using the predefined Diffie-Hellman private/public key pair as
|
/Zephyr-latest/doc/hardware/porting/ |
D | soc_porting.rst | 274 The entire file should be inside a pair of ``if SOC_<SOC_NAME>`` / ``endif``
|
/Zephyr-latest/subsys/net/lib/dns/ |
D | mdns_responder.c | 699 ctx->dispatcher.pair = NULL; in register_dispatcher()
|
/Zephyr-latest/boards/adi/max78002evkit/doc/ |
D | index.rst | 10 are supported, while a pair of industry-standard QWIIC connectors supports a large and growing arra…
|
/Zephyr-latest/doc/kernel/memory_management/ |
D | heap.rst | 119 It has a single pair of allocation entry points,
|
/Zephyr-latest/arch/arc/ |
D | Kconfig | 289 Depending on the configuration, CPU can contain accumulator reg-pair
|
/Zephyr-latest/modules/ |
D | Kconfig.mcuboot | 43 The file contains a key pair whose public half is verified
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.8.rst | 298 * ``ZEP-2027`` - Bluetooth Peripheral Sample won't pair with certain Android devices
|
/Zephyr-latest/subsys/net/lib/sockets/ |
D | Kconfig | 329 Communicate over a pair of connected, unnamed UNIX domain sockets.
|
1234