Searched refs:chunks (Results 1 – 14 of 14) sorted by relevance
| /Zephyr-Core-2.7.6/lib/os/ |
| D | heap.h | 75 static inline bool big_heap_chunks(chunksz_t chunks) in big_heap_chunks() argument
77 return sizeof(void *) > 4U || chunks > 0x7fffU; in big_heap_chunks()
|
| /Zephyr-Core-2.7.6/subsys/mgmt/hawkbit/ |
| D | hawkbit_priv.h | 135 struct hawkbit_dep_res_chunk chunks[HAWKBIT_DEP_MAX_CHUNKS]; member
|
| D | hawkbit.c | 211 JSON_OBJ_DESCR_OBJ_ARRAY(struct hawkbit_dep_res_deploy, chunks,
523 chunk = &res->deployment.chunks[0]; in hawkbit_parse_deployment()
584 struct hawkbit_dep_res_chunk *c = &d->deployment.chunks[0]; in hawkbit_dump_deployment()
|
| /Zephyr-Core-2.7.6/doc/reference/kernel/memory/ |
| D | heap.rst | 62 Internally, the ``sys_heap`` memory block is partitioned into "chunks"
64 chunks. The first chunk of every allocation or unused block is
69 unused chunks are added.
74 chunks, another for 5-8, 9-16, etc...) this allows new allocations to
|
| /Zephyr-Core-2.7.6/drivers/flash/ |
| D | Kconfig.nrf | 77 When this option is enabled writing chunks less than minimal write
|
| /Zephyr-Core-2.7.6/scripts/ |
| D | checkpatch.pl | 1559 my (@chunks);
1565 push(@chunks, [ $condition, $statement ]);
1567 return ($level, $linenr, @chunks);
1578 push(@chunks, [ $condition, $statement ]);
1581 return ($level, $linenr, @chunks);
5453 my ($level, $endln, @chunks) =
5457 if ($#chunks > 0 && $level == 0) {
5463 for my $chunk (@chunks) {
5524 my ($level, $endln, @chunks) =
5528 my ($cond, $block) = @{$chunks[0]};
[all …]
|
| /Zephyr-Core-2.7.6/scripts/kconfig/ |
| D | kconfiglib.py | 1467 chunks = [header] # "".join()ed later
1468 add = chunks.append
1501 return "".join(chunks)
1599 chunks = [header] # "".join()ed later
1600 add = chunks.append
1628 return "".join(chunks)
1701 chunks = [header] # "".join()ed later
1702 add = chunks.append
1729 return "".join(chunks)
|
| /Zephyr-Core-2.7.6/doc/reference/kernel/data_passing/ |
| D | pipes.rst | 7 to another thread. Pipes can be used to transfer chunks of data in whole
|
| /Zephyr-Core-2.7.6/doc/reference/logging/ |
| D | index.rst | 401 Each log message consists of one or more fixed size chunks allocated from the
408 log message is formed from multiple chunks which are linked together. When
432 * Memory is better utilized because fixed size chunks are not used.
|
| /Zephyr-Core-2.7.6/doc/guides/debug_tools/tracing/ |
| D | index.rst | 298 means data is copied-in in larger chunks than request-size.
|
| /Zephyr-Core-2.7.6/doc/reference/data_structures/ |
| D | ring_buffers.rst | 18 chunks of up to 1020 bytes. Each data item also has two
|
| /Zephyr-Core-2.7.6/doc/releases/ |
| D | release-notes-2.2.rst | 595 * Fix Websocket to receive data in small chunks
|
| D | release-notes-2.0.rst | 1358 * :github:`13799` - usb cdc acm fails when writing big chunks of data on stm32
|
| /Zephyr-Core-2.7.6/samples/modules/tflite-micro/hello_world/train/ |
| D | train_hello_world_model.ipynb | 329 "# split. We provide two indices, so the data will be divided into three chunks.\n",
|
