Home
last modified time | relevance | path

Searched full:kinds (Results 1 – 25 of 27) sorted by relevance

12

/Zephyr-latest/scripts/
Dvalgrind.supp4 match-leak-kinds: reachable
13 match-leak-kinds: reachable,possible
21 match-leak-kinds: reachable,possible
30 match-leak-kinds: reachable
38 match-leak-kinds: possible
45 match-leak-kinds: possible
Dtags.sh70 --extra=+f --c-kinds=+px \
/Zephyr-latest/boards/arduino/opta/dts/bindings/
Dgpio-power-switches.yaml6 or other kinds of power switches controlled by a GPIO. Each power
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dtriggers.rst12 There are many kinds of triggers sensors provide, from informative ones such as
/Zephyr-latest/scripts/build/
Dgen_relocate_app.py289 # Pass through section kinds that go into this memory region
300 Get the section kinds requested by the given memory region name.
303 follow the region name. If no kinds are specified all are assumed.
305 In addition to the parsed kinds, the input region minus specifiers for those
306 kinds is returned.
318 # No listed kinds implies all of the kinds
/Zephyr-latest/doc/services/pm/
Dsystem.rst93 or various kinds of minimum and maximum latency values, depending on the policy.
/Zephyr-latest/subsys/tracing/
DKconfig60 Enable tracing for testing kinds of format purpose. It must
/Zephyr-latest/subsys/bluetooth/host/
Dbuf.c23 * It's true that we don't put all kinds of events there (yet). However, the
/Zephyr-latest/doc/_extensions/zephyr/
Ddoxybridge.py61 """Mapping between Doxygen memberdef kind and Sphinx kinds"""
/Zephyr-latest/doc/services/sensing/
Dindex.rst158 For a sensor instance, could have two kinds of clients:
/Zephyr-latest/arch/arc/core/
Disr_wrapper.S73 ARCv2 processors have two kinds of interrupts: fast (FIRQ) and regular. The
/Zephyr-latest/arch/x86/
DKconfig406 mitigate against certain kinds of side channel attacks. Quoting
/Zephyr-latest/drivers/timer/
Dnpcx_itim_timer.c14 * 64/32-bit timers in Nuvoton NPCX series. Via these two kinds of timers, the
/Zephyr-latest/doc/security/
Dsecure-coding.rst200 At least one of the primary developers **must** know of common kinds of
/Zephyr-latest/tests/kernel/device/src/
Dmain.c61 * Validates three kinds situations of driver object:
/Zephyr-latest/doc/build/dts/
Dphandles.rst277 kinds of resources at the same time. The node describes the amount of metadata
/Zephyr-latest/drivers/rtc/
Drtc_pcf8563.c337 * There are several kinds of alarms, but here we only need to know that anything but 0 in pcf8563_alarm_is_pending()
/Zephyr-latest/include/zephyr/sys/
Ddevice_mmio.h585 * Either use Zephyr's driver model for these kinds of devices, or
/Zephyr-latest/doc/kernel/usermode/
Dsyscalls.rst561 When verifying system calls, it's important to note which kinds of verification
/Zephyr-latest/tests/kernel/smp/src/
Dmain.c1075 * We show the 4 kinds of scenario:
/Zephyr-latest/doc/services/zbus/
Dindex.rst850 * :zephyr:code-sample:`zbus-work-queue` shows how to define and use different kinds of observers.
/Zephyr-latest/tests/kernel/mem_protect/mem_protect/src/
Dkobject.c1243 * @details Allocate all kinds of kernel object and do permission
/Zephyr-latest/boards/phytec/reel_board/doc/
Dindex.rst18 Zephyr OS in these kinds of use cases:
/Zephyr-latest/doc/releases/
Drelease-notes-2.3.rst813 * :github:`25519` - wrong debug function cause kinds of building error
/Zephyr-latest/drivers/dai/intel/ssp/
Dssp.c2271 * For power saving, we should do kinds of power release when the SSP

12