Searched refs:vary (Results 1 – 25 of 30) sorted by relevance
12
| /Zephyr-latest/samples/basic/hash_map/ |
| D | Kconfig | 10 to vary the number of entries to insert or remove from the hash table
|
| /Zephyr-latest/tests/lib/hash_map/ |
| D | Kconfig | 10 to vary the number of entries to insert or remove from the hash table
|
| /Zephyr-latest/drivers/sensor/maxim/max30101/ |
| D | Kconfig | 105 measured LED current for each part can vary significantly due to the
119 measured LED current for each part can vary significantly due to the
133 actual measured LED current for each part can vary significantly due
|
| /Zephyr-latest/samples/drivers/kscan/ |
| D | README.rst | 20 because they vary across different manufactures).
|
| /Zephyr-latest/tests/benchmarks/wait_queues/ |
| D | README.rst | 7 the performance of these two implementations vary under varying conditions.
|
| /Zephyr-latest/tests/benchmarks/sched_queues/ |
| D | README.rst | 6 different performance characteristics that vary as the
|
| /Zephyr-latest/tests/bluetooth/controller/ctrl_isoal/ |
| D | Kconfig | 66 Needed margin for reliable delivery of payloads will vary, but should
|
| /Zephyr-latest/doc/project/ |
| D | working_groups.rst | 26 - The minimal number of members may vary depending on the complexity of the
32 optimal size of a working group can vary depending on the specific context and
|
| /Zephyr-latest/drivers/sensor/nxp/fxos8700/ |
| D | Kconfig | 40 uncalibrated and its output for a given temperature may vary from one
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | dma.rst | 18 requirements vary dramatically depending on the application. See :ref:`cache_guide` for an
|
| /Zephyr-latest/drivers/wifi/esp_at/ |
| D | Kconfig.esp_at | 93 sent. This can vary with chipset (ESP8266/ESP32) and firmware
|
| /Zephyr-latest/doc/develop/languages/c/ |
| D | newlib.rst | 84 The internal heap allocator implemented by the Newlib may vary across the
|
| /Zephyr-latest/boards/silabs/dev_kits/sltb010a/doc/ |
| D | index.rst | 86 to determine which one you have, as the GPIO pin bindings vary between those two.
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | blob_cli.rst | 74 list of Target nodes is extensive, and the effectiveness of each addressing strategy will vary
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig | 37 specifications, like pages, sectors or blocks, and may vary
|
| /Zephyr-latest/doc/services/binary_descriptors/ |
| D | index.rst | 36 to a known offset in the binary image. This offset may vary between architectures,
|
| /Zephyr-latest/drivers/bluetooth/hci/ |
| D | Kconfig | 49 prepended after a known header. Headers may vary per device, so
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | tls_credentials_shell.rst | 200 …representing the credential contents. The exact nature of this digest may vary depending on creden…
|
| /Zephyr-latest/samples/subsys/usb/mass/ |
| D | README.rst | 236 which produces output like this (disk contents will vary):
|
| /Zephyr-latest/doc/kernel/ |
| D | timeutil.rst | 25 constant and can vary widely over the runtime of a Zephyr application.
|
| /Zephyr-latest/doc/kernel/usermode/ |
| D | kernelobjects.rst | 131 * An extra data field. The semantics of this field vary by object type, see
|
| /Zephyr-latest/doc/develop/languages/cpp/ |
| D | index.rst | 211 C++20. Other standard revisions may vary. In doubt, do not rely on
|
| /Zephyr-latest/doc/contribute/ |
| D | bin_blobs.rst | 27 Most binary blobs are distributed under proprietary licenses which vary
|
| /Zephyr-latest/doc/services/tfm/ |
| D | overview.rst | 199 …-M 1.8.0, the following secure services are generally available (although vendor support may vary):
|
| /Zephyr-latest/doc/build/dts/api/ |
| D | api.rst | 327 contents vary by platform, and which describe a pin configuration for the node.
|
12
