Lines Matching full:used
7 based. Use of these macros has no impact on scheduling. They can be used from
11 macro named ``DT_DRV_COMPAT`` to be defined before they can be used; these are
13 :ref:`device drivers <device_model_api>`, though they can be used outside of
24 The APIs in this section can be used anywhere and do not require
40 used to create node identifiers for a given node's parent node or a particular
52 The following general-purpose macros can be used to access node properties.
68 devicetree specification, these macros can be used even for nodes without
85 devicetree specification, these macros can be used even for nodes without
99 some of these macros can be used even for nodes without matching bindings. This
123 This section documents miscellaneous macros that can be used to test if a node
125 properties, etc. Some macros used for special purposes (such as
175 the following APIs may be used.
233 The following APIs can also be used by including ``<devicetree.h>``;
241 These conveniences may be used for nodes which describe CAN
249 These conveniences may be used for nodes which describe clock sources, and
257 These conveniences may be used for nodes which describe direct memory access
267 These conveniences may be used for the special-purpose ``fixed-partitions``
268 compatible used to encode information about flash memory partitions in the
278 These conveniences may be used for nodes which describe GPIO controllers/pins,
286 These are commonly used by device drivers which need to use IO
296 These conveniences may be used for nodes which describe MBOX controllers/users,
306 These are used to access pin control properties by name or index.
334 These conveniences may be used for nodes which describe PWM controllers and
342 These conveniences may be used for nodes which describe reset controllers and
350 These conveniences may be used for nodes which describe either SPI controllers
361 system-wide settings. The :c:macro:`DT_CHOSEN()` macro can be used to get a node
369 The following table documents some commonly used Zephyr-specific chosen nodes.
371 Sometimes, a chosen node's label property will be used to set the default value
375 option, and the devicetree node is used directly in the source code to select a
387 - Selects the UART used for host communication in the
390 - Sets UART device used for the Bluetooth monitor logging
392 - Selects the HCI device used by the Bluetooth host stack
401 - Sets UART device used by console driver
409 - A device which can be used as a system-wide entropy source
411 - A node whose ``reg`` is sometimes used to set the defaults for
417 - Sets UART device used by the :ref:`gdbstub` subsystem
419 - Used by the networking subsystem to set the IEEE 802.15.4 device
421 - Used by the OpenAMP subsystem to specify the inter-process communication
424 - A node whose ``reg`` is used by the OpenAMP subsystem to determine the
430 - Sets the UART device(s) used by the logging subsystem's UART backend.
435 - Sets UART device used by OSDP subsystem
437 - Used by the OpenThread to specify UART device for Spinel protocol
441 - Sets UART device used by PPP
443 - Fixed partition node. If defined this selects the partition used
446 - Sets UART device used by serial shell backend
449 available to the Zephyr image, used during linking
451 - Sets UART device used by tracing subsystem
453 - UART used for :ref:`device_mgmt`
455 - Sets UART device used by serial pipe driver
458 will be used by the USB subsystem to enable/disable VBUS
460 - A LED-strip node which is used to determine the timings of the