Home
last modified time | relevance | path

Searched full:determine (Results 1 – 25 of 458) sorted by relevance

12345678910>>...19

/Zephyr-latest/dts/bindings/usb/
Dsnps,dwc2.yaml38 Value of the GHWCFG1 register. It is used to determine available endpoint
45 Value of the GHWCFG2 register. It is used to determine available endpoint
52 Value of the GHWCFG4 register. It is used to determine available endpoint
/Zephyr-latest/doc/build/dts/
Ddesign.rst20 - New device drivers shall use devicetree APIs to determine which :ref:`devices
24 determine which of multiple possible generic devices of a given type will be
26 determine the LED to blink.
35 determine the hardware supported by a board. This should be obtained from
38 - Legacy device drivers currently use Kconfig to determine which instances of a
/Zephyr-latest/include/zephyr/logging/
Dlog_frontend.h22 * @ref log_const_source_id or @ref log_dynamic_source_id can be used to determine
42 * @ref log_const_source_id or @ref log_dynamic_source_id can be used to determine
56 * @ref log_const_source_id or @ref log_dynamic_source_id can be used to determine
71 * @ref log_const_source_id or @ref log_dynamic_source_id can be used to determine
/Zephyr-latest/boards/digilent/arty_a7/
Dboard.h30 * @brief Determine if the DAPlink shield is fitted.
32 * Determine if the DAPlink shield is fitted based on the state of the
/Zephyr-latest/subsys/fs/ext2/
DKconfig30 This flag is used to determine size of internal structures that
37 This flag is used to determine size of internal structures that
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_timeout.rst38 #. Use :c:func:`net_timeout_evaluate()` to determine how long it is until the
41 again to determine whether the timeout has completed, or whether there is
51 determine the next timeout event to occur.
/Zephyr-latest/subsys/bluetooth/host/classic/
Davrcp_internal.h70 * within the target. These fields enable the target to determine whether the command is
76 * within the target. These fields enable the target to determine whether the command is
86 * within the target. These fields enable the target to determine whether the command is
93 * within the target. These fields enable the target to determine whether the command is
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dsar_cfg_cli.rst17 The SAR Transmitter procedure is used to determine and configure the SAR Transmitter state of a SAR
22 The SAR Receiver procedure is used to determine and configure the SAR Receiver state of a SAR
/Zephyr-latest/subsys/usb/device/
Dusb_descriptor.h17 * Use this macro to determine the length of the bString array.
34 * Use this macro to determine the bLength of the string descriptor.
/Zephyr-latest/include/zephyr/drivers/usb_c/
Dusbc_tc.h160 * @brief Minimum time a port shall wait before it can determine it is attached
166 * @brief Maximum time a port shall wait before it can determine it is attached
172 * @brief Minimum time a Sink port shall wait before it can determine it is detached due to
179 * @brief Maximum time a Sink port shall wait before it can determine it is detached due to
186 * @brief Minimum Time a port shall wait before it can determine it is re-attached during
193 * @brief Maximum Time a port shall wait before it can determine it is re-attached during
213 * @brief Minimum time a Sink port shall wait before it can determine there has been a change
220 * @brief Maximum time a Sink port shall wait before it can determine there has been a change
/Zephyr-latest/soc/nxp/lpc/lpc54xxx/gcc/
Dstartup_LPC54114_cm4.S34 * Determine if the core executing this code is the master or
47 /* Determine which core (M0+ or M4) this code is running on */
60 /* Determine if M4 core is the master or slave */
/Zephyr-latest/dts/bindings/sensor/
Dnxp,s32-qdec.yaml5 Quadrature Decoder driver which processes encoder signals to determine motor revs
51 This is a number that is used to determine how many revolutions * 1000000
106 This array configures the input indices to the LCU module which help to determine the
Dst,stm32-vref.yaml22 VDDA/VREF+ voltage in millivolts applied during manufacturing to determine
/Zephyr-latest/dts/bindings/input/
Dgoodix,gt911.yaml19 use probing mode to determine the I2C address rather than setting the
/Zephyr-latest/dts/bindings/can/
Drenesas,ra-canfd.yaml24 To determine the maximum rx filters can be added on this CAN device.
/Zephyr-latest/doc/hardware/peripherals/sensor/
Dtriggers.rst9 then commonly be inspected by reading registers to determine which event caused
/Zephyr-latest/drivers/sensor/adi/adxl367/
DKconfig85 compared directly to a user set threshold to determine whether
94 compared directly to a user set threshold to determine whether
/Zephyr-latest/doc/kernel/usermode/
Dmpu_stack_objects.rst58 that covers the memory access to determine the enforcement policy. Others may
59 logically OR regions to determine enforcement policy.
/Zephyr-latest/subsys/shell/modules/kernel_service/thread/
DKconfig9 Internal helper macro to determine if the main `thread` command
/Zephyr-latest/doc/security/
Dreporting.rst58 response team will analyze the issue, determine a responsible
96 attendance. During this review, they shall determine if new issues
145 vetted by the project director to determine that they have a
154 to determine if they need to backport these changes to any internal
/Zephyr-latest/drivers/sensor/microchip/mchp_tach_xec/
DKconfig22 will be used to determine the interval for which the number of
/Zephyr-latest/doc/hardware/peripherals/
Dhwinfo.rst12 Reset cause flags can be used to determine why the device was reset; for
/Zephyr-latest/dts/bindings/i3c/
Di3c-controller.yaml31 Virtual Register (LVR) of all connected I2C devices to determine
/Zephyr-latest/cmake/toolchain/xt-clang/
Dgeneric.cmake13 # command line arguments while invoking xt-clang to determine
/Zephyr-latest/samples/boards/google/twinkie_v2/pda/
DREADME.rst5 Implement a basic Power Delivery Analyzer to determine if a USB device is currently charging.

12345678910>>...19