Lines Matching full:devicetree

3 Devicetree HOWTOs
6 This page has step-by-step advice for getting things done with devicetree.
10 .. _get-devicetree-outputs:
12 Get your devicetree and generated header
15 A board's devicetree (:ref:`BOARD.dts <devicetree-in-out-files>`) pulls in
17 includes the SoC's ``.dtsi``. One way to figure out the devicetree's contents
21 If you just want to see the "final" devicetree for your board, build an
26    You can build :ref:`hello_world` to see the "base" devicetree for your board
47 The :file:`zephyr.dts` file is the final devicetree in DTS format.
51 See :ref:`devicetree-in-out-files` for details about these files.
55 Get a struct device from a devicetree node
59 :ref:`struct device <device_model_api>` corresponding to a devicetree node.
61 For example, with this devicetree fragment, you might want the struct device
64 .. code-block:: devicetree
149 devicetree. If you don't see the ``#error`` but ``uart_dev`` is NULL, then
155 Find a devicetree binding
162 If you don't have them already, :ref:`get-devicetree-outputs`. To find a node's
187     * Devicetree node:
197 .. _set-devicetree-overlays:
199 Set devicetree overlays
202 Devicetree overlays are explained in :ref:`devicetree-intro`. The CMake
226 The :ref:`build system <build_overview>` prints all the devicetree overlays it
231    -- Found devicetree overlay: .../some/file.overlay
235 Use devicetree overlays
238 See :ref:`set-devicetree-overlays` for how to add an overlay to the build.
243 .. code-block:: devicetree
272 You can add aliases to your devicetree using overlays: an alias is just a
348 Write device drivers using devicetree APIs
351 "Devicetree-aware" :ref:`device drivers <device_model_api>` should create a
352 ``struct device`` for each ``status = "okay"`` devicetree node with a
363   This style predates support for devicetree in Zephyr and its use is now
364   discouraged. Existing device drivers may be made "devicetree-aware"
367 Writing a devicetree-aware driver begins by defining a :ref:`devicetree binding
380 After writing your binding, your driver C file can then use the devicetree API
387 - Each ``struct device``\ 's name should be set to its devicetree node's
391 - Each device's initial configuration should use values from devicetree
393   using :ref:`devicetree overlays <use-dt-overlays>`.
425 Use this option, which uses :ref:`devicetree-inst-apis`, if possible. However,
426 they only work when devicetree nodes for your driver's ``compatible`` are all
432 devicetree, you would define ``DT_DRV_COMPAT`` to ``vnd_my_device`` in your
478 :c:func:`DEVICE_DT_INST_DEFINE` to access devicetree node data. These
479 APIs retrieve data from the devicetree for instance number ``inst`` of
501 :c:func:`DT_NODELABEL` to refer to individual nodes in the devicetree
502 representing the supported peripherals on the SoC. The devicetree.h
503 :ref:`devicetree-generic-apis` can then be used to access node data.
507 your driver supports. The resulting devicetree usually looks something like
510 .. code-block:: devicetree
524 devicetree to operate on specific device nodes:
555 :c:func:`DEVICE_DT_DEFINE` to access devicetree node data.
557 Finally, manually detect each enabled devicetree node and use
583 - Write your devicetree binding in a way that permits use of
584   :ref:`devicetree-hw-api` from devicetree.h if possible.
599 supporting a devicetree alias to specify the hardware specific portions, as is
601 :ref:`BOARD.dts <devicetree-in-out-files>` files or via :ref:`devicetree