| /Zephyr-latest/subsys/mgmt/mcumgr/transport/ |
| D | Kconfig | 45 The size, in bytes, of each mcumgr buffer. This value must satisfy
66 The size, in bytes, of user data to allocate for each mcumgr buffer.
|
| D | Kconfig.dummy | 26 in bytes. This value must be large enough to accommodate any
|
| /Zephyr-latest/samples/drivers/ipm/ipm_esp32/ |
| D | README.rst | 18 any application, each channel supports up to 64 bytes of data per
20 messages in chunks of 64 bytes.
|
| /Zephyr-latest/tests/bluetooth/controller/ctrl_isoal/ |
| D | Kconfig | 47 int "Minimum number of playload data bytes in a new segment"
52 Minimum number of payload bytes that would make inserting a new
|
| /Zephyr-latest/subsys/mgmt/mcumgr/grp/fs_mgmt/ |
| D | Kconfig | 38 This option decides on number of bytes that are reserved in
44 Files that have size up to 64KB require 1 to 3 bytes to encode
50 Files that have size up to 4GB require 1 to 5 bytes to encode
86 number of bytes that, with all the required headers, will fit
155 Limits the maximum path length for file operations, in bytes. A buffer
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | pipes.rst | 31 thread. If the specified minimum number of bytes can not be immediately
33 as many bytes as possible and then pend in the hope that the send can be
38 minimum number of bytes can not be immediately satisfied, then the operation
39 will either fail immediately or attempt to receive as many bytes as possible
69 buffer capable of holding 100 bytes and is aligned to a 4-byte boundary.
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icmsg.rst | 113 If cache is not enabled, the required alignment is 4 bytes.
123 - Size (bytes)
141 - Circular buffer containing actual bytes to transfer.
161 - Size (bytes)
180 - Padding is added to align the total packet size to 4 bytes.
|
| D | ipc_service_icbmsg.rst | 135 …* ICMsg message size for 4 bytes of content (refer to the ICMsg specification) multiplied by ``loc…
176 #. The sender wants to send a message that contains ``K`` bytes.
177 …e sender reserves blocks from his ``tx-region`` blocks area that can hold at least ``K + 4`` bytes.
178 …The additional ``+ 4`` bytes are reserved for the header, which contains the exact size of the mes…
205 Each control message contains three bytes.
339 * - bytes 0-3
340 - bytes 4-10
388 * If the receiver receives a longer control message, it should use only the first three bytes and i…
390 …eiver receives a binding message with additional bytes at the end, it should ignore the additional…
|
| /Zephyr-latest/doc/connectivity/networking/ |
| D | eth_bridge_native_sim_setup.rst | 39 RX packets 33 bytes 2408 (2.4 KB)
41 TX packets 49 bytes 4092 (4.0 KB)
49 RX packets 21 bytes 1340 (1.3 KB)
51 TX packets 45 bytes 3916 (3.9 KB)
|
| /Zephyr-latest/boards/beagle/beaglev_fire/doc/ |
| D | index.rst | 122 . 0 bytes written, 0 bytes read
124 / 0 bytes written, 219136 bytes read
|
| /Zephyr-latest/drivers/w1/ |
| D | Kconfig.zephyr_serial | 16 via bytes read and write operations on top of the Zephyr
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.signal | 36 Will use 256 bytes of ROM.
|
| /Zephyr-latest/tests/drivers/uart/uart_mix_fifo_poll/ |
| D | README.txt | 5 any bytes being dropped.
|
| /Zephyr-latest/samples/drivers/ipm/ipm_ivshmem/ |
| D | README.rst | 101 Shared memory: 0xafa00000 of size 4194304 bytes
117 Shared memory: 0xafa00000 of size 4194304 bytes
129 Shared memory: 0xafa00000 of size 4194304 bytes
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | shell.rst | 321 …oned device. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
337 …oned device. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
347 … UUID value. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
378 … static OOB. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
440 …c OOB value. Providing a hex-string shorter than 32 bytes will populate the N most significant byt…
642 …cimal value. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
651 …cimal value. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
675 …cimal value. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
684 …cimal value. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
774 … publish to. Providing a hex-string shorter than 16 bytes will populate the N most significant byt…
[all …]
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | bbram.rst | 12 - Size - get the size (in bytes) of the BBRAM region.
|
| /Zephyr-latest/drivers/wifi/eswifi/ |
| D | eswifi_socket_offload.c | 176 int i, bytes; in map_credentials() local
210 bytes = strlen(eswifi->buf); in map_credentials()
211 memcpy(&eswifi->buf[bytes], cert->buf, cert->len); in map_credentials()
212 bytes += cert->len; in map_credentials()
214 ret = eswifi_request(eswifi, eswifi->buf, bytes + 1, in map_credentials()
|
| /Zephyr-latest/boards/shields/lcd_par_s035/boards/ |
| D | rd_rw612_bga.overlay | 79 * color format. This is because the "nxp,swap-bytes" setting
93 nxp,swap-bytes;
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.stm32 | 89 bool "Extended operation for option bytes access"
94 STM32 option bytes.
|
| /Zephyr-latest/drivers/espi/ |
| D | Kconfig.it8xxx2 | 135 # It means that the Host must alwasy write 2 bytes of data to port 80 otherwise
142 This allows EC to accept 2 bytes of port 80 data written from the Host.
|
| /Zephyr-latest/drivers/wifi/esp32/src/ |
| D | esp_wifi_drv.c | 109 data->stats.bytes.sent += pkt_len; in esp32_wifi_send()
153 esp32_data.stats.bytes.received += len; in eth_esp32_rx()
200 esp32_ap_sta_data.stats.bytes.received += len; in wifi_esp32_ap_iface_rx()
878 stats->bytes.received = data->stats.bytes.received; in esp32_wifi_stats()
879 stats->bytes.sent = data->stats.bytes.sent; in esp32_wifi_stats()
|
| /Zephyr-latest/doc/kernel/services/other/ |
| D | float.rst | 112 an extra 72 bytes of stack space where the callee-saved FP context can
159 Each thread object becomes 512 bytes larger when Shared FP registers mode
186 context of threads that are not using the FP registers. An extra 16 bytes
187 (single floating point hardware) or 32 bytes (double floating point hardware)
221 Each thread object becomes 136 bytes (single-precision floating point
222 hardware) or 264 bytes (double-precision floating point hardware) larger
248 When :kconfig:option:`CONFIG_FPU_SHARING` is used, then 136 bytes of stack space
267 cooperative any 0 bytes
268 preemptive none 0 bytes
269 preemptive FPU 108 bytes
[all …]
|
| /Zephyr-latest/subsys/bluetooth/audio/ |
| D | Kconfig.mcs | 35 Sets the maximum number of bytes (including the null termination) of
44 Sets the maximum number of bytes (including the null termination) of
53 Sets the maximum number of bytes (including the null termination) of
62 Sets the maximum number of bytes (including the null termination)
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | sys_mem_blocks.rst | 32 * The **block size** of each block, measured in bytes.
33 It must be at least 4N bytes long, where N is greater than 0.
39 It must be at least "block size" times "number of blocks" bytes long.
108 which has 4 blocks that are 64 bytes long, each of which is aligned
|
| /Zephyr-latest/lib/hash/ |
| D | Kconfig.hash_func | 38 either 1, 2, 4, or 8 bytes in length and so is suitable for scalar
|
