Home
last modified time | relevance | path

Searched full:vary (Results 1 – 25 of 43) sorted by relevance

12

/Zephyr-Core-3.6.0/tests/lib/hash_map/
DKconfig10 to vary the number of entries to insert or remove from the hash table
/Zephyr-Core-3.6.0/drivers/sensor/max30101/
DKconfig105 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-Core-3.6.0/samples/basic/hash_map/
DKconfig10 to vary the number of entries to insert or remove from the hash table
/Zephyr-Core-3.6.0/dts/bindings/clock/
Dst,stm32f4-plli2s-clock.yaml29 Valid range may vary between parts: 50 - 432 , 192 - 432
/Zephyr-Core-3.6.0/samples/drivers/kscan/
DREADME.rst20 because they vary across different manufactures).
/Zephyr-Core-3.6.0/dts/bindings/gpio/
Dmikro-bus.yaml28 Board's silkscreen may vary depending on your board, but coherent with
/Zephyr-Core-3.6.0/drivers/sensor/fxos8700/
DKconfig40 uncalibrated and its output for a given temperature may vary from one
/Zephyr-Core-3.6.0/soc/xtensa/intel_adsp/common/include/
Dadsp_debug_window.h32 * The overall number of slots can vary based on platform.
/Zephyr-Core-3.6.0/drivers/wifi/esp_at/
DKconfig.esp_at93 sent. This can vary with chipset (ESP8266/ESP32) and firmware
/Zephyr-Core-3.6.0/dts/bindings/mtd/
Datmel,sam-flash.yaml116 the erase-blocks, which can vary in size within the flash memory
/Zephyr-Core-3.6.0/dts/bindings/pinctrl/
Dmicrochip,xec-pinctrl.yaml38 Driver strength and slew rate hardware defaults vary by SoC and pin.
/Zephyr-Core-3.6.0/tests/kernel/spinlock/src/
Dspinlock_fairness.c110 * vary between the CPU cores, so that some CPUs reach the spinlock faster
/Zephyr-Core-3.6.0/drivers/bluetooth/hci/
DKconfig54 prepended after a known header. Headers may vary per device, so
/Zephyr-Core-3.6.0/arch/arm/core/mmu/
Darm_mmu_priv.h55 * The following defines might vary if support for CPUs without
/Zephyr-Core-3.6.0/doc/develop/languages/c/
Dnewlib.rst84 The internal heap allocator implemented by the Newlib may vary across the
/Zephyr-Core-3.6.0/doc/connectivity/bluetooth/api/mesh/
Dblob_cli.rst74 list of Target nodes is extensive, and the effectiveness of each addressing strategy will vary
/Zephyr-Core-3.6.0/doc/services/binary_descriptors/
Dindex.rst36 to a known offset in the binary image. This offset may vary between architectures,
/Zephyr-Core-3.6.0/include/zephyr/drivers/
Dipm.h177 * IPM implementations vary on the amount of data that can be sent in a
/Zephyr-Core-3.6.0/include/zephyr/sys/
Dkobject.h228 * their sizes can vary. Other objects should probably look k_object_alloc().
/Zephyr-Core-3.6.0/samples/bluetooth/ipsp/
DREADME.rst64 (may vary slightly by application and Zephyr versions):
/Zephyr-Core-3.6.0/drivers/mipi_dbi/
Dmipi_dbi_spi.c44 * displays may vary.
/Zephyr-Core-3.6.0/doc/connectivity/networking/api/
Dtls_credentials_shell.rst200 …representing the credential contents. The exact nature of this digest may vary depending on creden…
/Zephyr-Core-3.6.0/samples/bluetooth/peripheral_csc/src/
Dmain.c325 * notified approximately once per second. This interval may vary in csc_simulation()
/Zephyr-Core-3.6.0/samples/subsys/usb/mass/
DREADME.rst236 which produces output like this (disk contents will vary):
/Zephyr-Core-3.6.0/tests/kernel/events/event_api/src/
Dtest_event_apis.c65 * The type of wait queue used by the event may vary depending upon in ZTEST()

12