Lines Matching full:devicetree

3 Devicetree API
6 This is a reference page for the ``<devicetree.h>`` API. The API is macro
26 A *node identifier* is a way to refer to a devicetree node at C preprocessor
28 devicetree data in C rvalue form using, for example, the
29 :ref:`devicetree-property-access` API.
32 identifiers for other devicetree nodes using :c:func:`DT_PATH`,
41 .. doxygengroup:: devicetree-generic-id
49 There are special-purpose APIs for accessing the :ref:`devicetree-reg-property`
50 and :ref:`devicetree-interrupts-property`.
55 .. doxygengroup:: devicetree-generic-prop
62 Use these APIs instead of :ref:`devicetree-property-access` to access the
64 devicetree specification, these macros can be used even for nodes without
67 .. doxygengroup:: devicetree-reg-prop
74 Use these APIs instead of :ref:`devicetree-property-access` to access the
77 Because this property's semantics are defined by the devicetree specification,
81 .. doxygengroup:: devicetree-interrupts-prop
88 devicetree node.
94 .. doxygengroup:: devicetree-generic-foreach
105 .. doxygengroup:: devicetree-generic-exist
112 The ``devicetree.h`` API has some support for tracking dependencies between
114 devicetree nodes, which is defined as the `transitive closure
123 A *dependency ordering* of a devicetree is a list of its nodes, where each node
126 distinct devicetree nodes ``n1`` and ``n2`` with dependency ordinals ``d1`` and
133 The Zephyr build system chooses a dependency ordering of the final devicetree
142 .. doxygengroup:: devicetree-dep-ord
147 Zephyr's devicetree bindings language supports a ``bus:`` key which allows
152 .. doxygengroup:: devicetree-generic-bus
161 implements support for. Here is an example devicetree fragment:
163 .. code-block:: devicetree
187 :ref:`devicetree-generic-apis`. The equivalent generic API can be found by
199 specific hardware; these are documented in :ref:`devicetree-hw-api`.
201 .. doxygengroup:: devicetree-inst
208 The following APIs can also be used by including ``<devicetree.h>``;
217 .. doxygengroup:: devicetree-clocks
225 .. doxygengroup:: devicetree-dmas
237 .. doxygengroup:: devicetree-fixed-partition
247 .. doxygengroup:: devicetree-gpio
255 .. doxygengroup:: devicetree-io-channels
264 Devicetree nodes may have properties which specify pin control (sometimes known
285 .. doxygengroup:: devicetree-pinctrl
293 .. doxygengroup:: devicetree-pwms
301 .. doxygengroup:: devicetree-spi
312 .. doxygengroup:: devicetree-generic-chosen
318 .. doxygengroup:: devicetree-zephyr
326 predates devicetree support in Zephyr. In other cases, there is no Kconfig
327 option, and the devicetree node is used directly in the source code to select a