Lines Matching full:devicetree

3 Troubleshooting devicetree
6 Here are some tips for fixing misbehaving devicetree related code.
18 This is general advice which is especially applicable to debugging devicetree
22 Make sure <devicetree.h> is included
25 Unlike Kconfig symbols, the :file:`devicetree.h` header must be included
28 Many Zephyr header files rely on information from devicetree, so including some
29 other API may transitively include :file:`devicetree.h`, but that's not
39 - In C/C++, devicetree names must be lowercased and special characters must be
40   converted to underscores. Zephyr's generated devicetree header has DTS names
42   ``<devicetree.h>`` API.
43 - In overlays, use devicetree node and property names the same way they
64 And if you're trying to **set** that property in a devicetree overlay:
72    /* Don't do this; you'll get devicetree errors. */
97 devicetree macros expanded to. For example, on macOS and Linux, using ``find``
135 isn't referring to a valid node. :ref:`get-devicetree-outputs` and debug from
155 binding. If the property is set, check for typos in its name. In a devicetree