Lines Matching full:devicetree

3 Troubleshooting devicetree
6 Here are some tips for fixing misbehaving devicetree related code.
20 This is general advice which is especially applicable to debugging devicetree
24 Make sure <devicetree.h> is included
27 Unlike Kconfig symbols, the :file:`devicetree.h` header must be included
30 Many Zephyr header files rely on information from devicetree, so including some
31 other API may transitively include :file:`devicetree.h`, but that's not
44 no device driver has allocated a ``struct device`` for this devicetree node.
67 To find the devicetree node you need to check, use the number ``<N>`` from the
92 devicetree for your application build. (See :ref:`get-devicetree-outputs` for
96 to enable it by setting ``status = "okay";``, probably by using a devicetree
97 :ref:`overlay <set-devicetree-overlays>`. For example, if :file:`zephyr.dts`
106 Then you should put this into your devicetree overlay and
121 your devicetree node and allocating devices for it. To do this, you need to
122 start with the ``compatible`` property in your devicetree node, and find the
125 If you're not familiar with how devices are allocated from devicetree nodes
128 :ref:`device_model_api` pages. See :ref:`dt-important-props` and the Devicetree
135 devicetree compatibles they are associated with. You will have to figure this
162 Continuing the above example, if your devicetree node looks like this now:
192 as you enable the devicetree node. Otherwise, it is sometimes as simple as
216 - In C/C++, devicetree names must be lowercased and special characters must be
217   converted to underscores. Zephyr's generated devicetree header has DTS names
219   ``<devicetree.h>`` API.
220 - In overlays, use devicetree node and property names the same way they
241 And if you're trying to **set** that property in a devicetree overlay:
249    /* Don't do this; you'll get devicetree errors. */
274 devicetree macros expanded to. For example, on macOS and Linux, using ``find``
295 Compiler messages for devicetree errors can sometimes be very long. This
330 isn't referring to a valid node. :ref:`get-devicetree-outputs` and debug from
350 binding. If the property is set, check for typos in its name. In a devicetree