Home
last modified time | relevance | path

Searched full:meaning (Results 1 – 25 of 107) sorted by relevance

12345

/Zephyr-Core-3.6.0/dts/bindings/phy/
Dphy-controller.yaml13 Number of cells in a PHY provider. The meaning those
/Zephyr-Core-3.6.0/dts/bindings/dac/
Dnxp,lpdac.yaml18 DAC voltage reference select. The meaning of the value may be
/Zephyr-Core-3.6.0/boards/posix/nrf_bsim/common/cmsis/
Dcmsis_instr.h111 * Meaning, it does not set a exclusive lock,
124 * Meaning, it does not set a exclusive lock,
137 * Meaning, it does not set a exclusive lock,
/Zephyr-Core-3.6.0/include/zephyr/net/
Dsocket_service.h115 * The user callback is called asynchronously for this service meaning that
138 * The user callback is called asynchronously for this service meaning that
153 * The user callback is called synchronously for this service meaning that
176 * The user callback is called synchronously for this service meaning that
/Zephyr-Core-3.6.0/drivers/dma/
DKconfig.mcux_lpc27 space by setting this value to suit its needs. The meaning of the value
/Zephyr-Core-3.6.0/dts/bindings/dma/
Despressif,esp32-gdma.yaml26 supported, meaning three transmit and three receive channels.
Dnxp,edma.yaml23 and "dma-channels" are mutually exclusive, meaning you
/Zephyr-Core-3.6.0/doc/_extensions/zephyr/
Ddtcompatible-role.py27 using its own role to avoid using one that already has a standard meaning.
/Zephyr-Core-3.6.0/subsys/bluetooth/audio/
DKconfig.ascs47 meaning the number of ASEs that are allowed to be in a non-idle state at
/Zephyr-Core-3.6.0/share/zephyr-package/cmake/
DZephyrConfigVersion.cmake18 # We are just a candidate, meaning we have been included from other installed module.
53 # meaning the package version must be ignored and the Zephyr pointed to by
/Zephyr-Core-3.6.0/dts/bindings/led_strip/
Dworldsemi,ws2812-rpi_pico-pio.yaml67 transmitted per second. It is same meaning as bit-per-seconds.
/Zephyr-Core-3.6.0/include/zephyr/arch/posix/
Dlinker.ld83 * Note that the INSERT command actually changes the meaning of the -T command
/Zephyr-Core-3.6.0/boards/posix/native_posix/
Dcpu_wait.c32 * running. Meaning, the SW running on the MCU is assumed to take 0 time.
/Zephyr-Core-3.6.0/boards/posix/native_sim/
Dcpu_wait.c35 * running. Meaning, the SW running on the MCU is assumed to take 0 time.
/Zephyr-Core-3.6.0/subsys/logging/backends/
Dlog_backend_adsp.c14 * to prevent concurrency. Meaning if log_process is called after
/Zephyr-Core-3.6.0/tests/bluetooth/df/connectionless_cte_tx/src/
Dcommon.c23 /* Example cte length value in allowed range, no particular meaning */
/Zephyr-Core-3.6.0/soc/x86/apollo_lake/doc/
Dsupported_features.txt56 and ``clock-frequency`` (the resulting baud master clock). The meaning of
/Zephyr-Core-3.6.0/kernel/include/
Dgen_offset.h24 * changing the meaning of an absolute symbol may require modifications to a
/Zephyr-Core-3.6.0/doc/hardware/peripherals/
Ddma.rst23 From an API point of view, a DMA channel is a single-owner object, meaning the drivers should not
/Zephyr-Core-3.6.0/soc/xtensa/intel_adsp/common/include/
Dcpu_init.h83 * "internal" operations, meaning they are atomic only WRT the in cpu_early_init()
/Zephyr-Core-3.6.0/drivers/fpga/
Dfpga_mpfs.c222 * offset For some services this field has another meaning. in verify_image()
270 * offset For some services this field has another meaning. in activate_image()
353 * offset For some services this field has another meaning. in mpfs_fpga_get_info()
/Zephyr-Core-3.6.0/doc/build/kconfig/
Dextensions.rst47 - Environment variables in ``source`` statements are expanded directly, meaning
/Zephyr-Core-3.6.0/doc/services/rtio/
Dindex.rst122 operations can be converted to a set of DMA transfer descriptors, meaning the
209 descriptors entirely. Meaning the hardware can potentially do more than ever.
/Zephyr-Core-3.6.0/drivers/net/
Dloopback.c113 /* We should simulate normal driver meaning that if the packet is in loopback_send()
/Zephyr-Core-3.6.0/doc/project/
Dproposals.rst58 assignee are open for grabs, meaning that they can be picked up and implemented

12345