Home
last modified time | relevance | path

Searched full:exactly (Results 1 – 25 of 186) sorted by relevance

12345678

/Zephyr-latest/dts/bindings/led_strip/
Dws2812-gpio.yaml15 led-strip. Exactly one pin should be given.
/Zephyr-latest/include/zephyr/tracing/
Dtracing_macros.h230 * @param func Name of the function responsible for the call. This does not need to exactly
243 * @param func Name of the function responsible for the call. This does not need to exactly
255 * @param func Name of the function responsible for the call. This does not need to exactly
269 * @param func Name of the function responsible for the call. This does not need to exactly
295 * @param func Name of the function responsible for the call. This does not need to exactly
314 * @param func Name of the function responsible for the call. This does not need to exactly
330 * @param func Name of the function responsible for the call. This does not need to exactly
349 * @param func Name of the function responsible for the call. This does not need to exactly
/Zephyr-latest/tests/bsim/bluetooth/host/l2cap/stress/
Dprj_nofrag.conf19 # 23+27+27=77 makes exactly three full packets
Dprj.conf19 # 23+27+27=77 makes exactly three full packets
Dprj_syswq.conf19 # 23+27+27=77 makes exactly three full packets
/Zephyr-latest/tests/bsim/bluetooth/host/l2cap/many_conns/
Dprj.conf19 # 23+27+27=77 makes exactly three full packets
/Zephyr-latest/cmake/emu/
Dsimics.cmake10 # Search exactly for the project's autogenerated 'trampoline' script.
/Zephyr-latest/doc/hardware/peripherals/
Dcoredump.rst12 A COREDUMP_TYPE_CALLBACK device requires exactly one entry in the memory-regions
/Zephyr-latest/samples/net/secure_mqtt_sensor_actuator/
DKconfig48 bool "QoS 2 / Exactly once delivery"
/Zephyr-latest/arch/x86/core/intel64/
Dsmp.c34 * it is not clear exactly how/where/why to abstract this, as it
/Zephyr-latest/subsys/mgmt/osdp/
DKconfig.cp20 string should exactly match the number of connected PDs specified above
/Zephyr-latest/dts/bindings/coredump/
Dzephyr,coredump.yaml23 A device of type COREDUMP_TYPE_CALLBACK must specify exactly one entry in the
/Zephyr-latest/dts/bindings/gpio/
Dpanasonic,reduced-arduino-header.yaml34 1. Power Supply header exactly, like on Arduino UNO layout.
/Zephyr-latest/samples/fuel_gauge/max17048/
DREADME.rst34 … the charging status change because it will not work. If you really need to know exactly the moment
/Zephyr-latest/.github/ISSUE_TEMPLATE/
D003_rfc-proposal.md41 By reading this section, each team member should be able to know what exactly
/Zephyr-latest/samples/shields/npm1300_ek/doc/
Dindex.rst62 # set BUCK2 voltage to exactly 2V
/Zephyr-latest/doc/services/task_wdt/
Dindex.rst33 to match exactly the number of channels required by the application.
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/priv_beacon/
Dproxy_adv_multi_subnet_coex.sh22 # window. The Mesh Protocol specification does not specify exactly the
/Zephyr-latest/tests/posix/common/src/
Dcond.c14 * @details Exactly CONFIG_MAX_PTHREAD_COND_COUNT can be in use at once.
/Zephyr-latest/soc/mediatek/mt8xxx/
Dirq.c12 /* Sort of annoying: assumes there are exactly two controller devices
/Zephyr-latest/lib/heap/
Dheap_validate.c85 return false; /* Should have exactly consumed the buffer */ in sys_heap_validate()
156 return false; /* Should have exactly consumed the buffer */ in sys_heap_validate()
/Zephyr-latest/soc/intel/intel_adsp/ace/
Dtimestamp.c36 /* Exactly one trigger bit must be set in a valid request */ in intel_adsp_get_timestamp()
/Zephyr-latest/doc/develop/west/
Dinstall.rst37 the user's filesystem (exactly where depends on the operating system, but
/Zephyr-latest/include/zephyr/dt-bindings/usb/
Daudio.h31 * Release 2.0 May 31, 2006 and Release 3.0 September 22, 2016 contain exactly
/Zephyr-latest/include/zephyr/sys/
Dheap_listener.h62 * @note The number of bytes allocated may not match exactly
81 * @note The number of bytes freed may not match exactly to

12345678