Lines Matching full:devicetree

3 Devicetree access from C/C++
6 This guide describes Zephyr's ``<zephyr/devicetree.h>`` API for reading the
7 devicetree from C source files. It assumes you're familiar with the concepts in
8 :ref:`devicetree-intro` and :ref:`dt-bindings`. See :ref:`dt-reference` for
14 Linux developers familiar with devicetree should be warned that the API
15 described here differs significantly from how devicetree is used on Linux.
17 Instead of generating a C header with all the devicetree data which is then
19 devicetree data structure in its binary form. The binary representation is
22 Zephyr does not work this way because the size of the devicetree binary and
31 To get information about a particular devicetree node, you need a *node
37    Use :c:func:`DT_PATH()` along with the node's full path in the devicetree,
76    :language: devicetree
90    devicetree names are converted to underscores (``_``). The names in a DTS
137 the :ref:`example devicetree <dt-node-main-ex>` above:
185 Here is an example devicetree fragment:
187 .. code-block:: devicetree
276 Most Zephyr devicetree bindings have a cell named ``irq``, which is the
282    Here, "processed" reflects Zephyr's devicetree :ref:`dt-scripts`, which
283    change the ``irq`` number in :ref:`zephyr.dts <devicetree-in-out-files>` to
310 the tree. In this case, you usually want to convert the devicetree-level
324 .. _other-devicetree-apis:
338 - :ref:`devicetree-flash-api`: APIs for managing fixed flash partitions.
356    #include <zephyr/devicetree.h>
369 See :ref:`devicetree-inst-apis` for a generic API reference.
375 readability for hardware specific code. See :ref:`devicetree-hw-api` for
381 While the :file:`zephyr/devicetree.h` API is not generated, it does rely on a
384 devicetree data.