Lines Matching +full:input +full:- +full:src

1 .. _devicetree-in-out-files:
3 Input and output files
6 This section describes the input and output files shown in the figure in
7 :ref:`devicetree-scope-purpose` in more detail.
10    :figclass: align-center
12    Devicetree input (green) and output (yellow) files
14 .. _dt-input-files:
16 Input files
19 There are four types of devicetree input files:
21 - sources (``.dts``)
22 - includes (``.dtsi``)
23 - overlays (``.overlay``)
24 - bindings (``.yaml``)
28 .. code-block:: none
40 describe the CPU or system-on-chip Zephyr runs on, perhaps by including other
46 include file for defining a complete devicetree. Architecture-specific
58 - Zephyr applications can use overlays to enable a peripheral that is disabled
63 - Overlays are also used when defining :ref:`shields`.
68 :ref:`set-devicetree-overlays` for details.
78 :ref:`dt-bindings` (which are YAML files) are essentially glue. They describe
83 .. _dt-scripts:
89 create output files from input files. Their sources have extensive
92 :zephyr_file:`dtlib.py <scripts/dts/python-devicetree/src/devicetree/dtlib.py>`
93     A low-level DTS parsing library.
95 :zephyr_file:`edtlib.py <scripts/dts/python-devicetree/src/devicetree/edtlib.py>`
97     properties and give a higher-level view of the devicetree. Uses dtlib to do
100 :zephyr_file:`gen_defines.py <scripts/dts/python-devicetree/src/devicetree/edtlib.py>`
111 .. code-block:: cmake
113    list(APPEND EXTRA_DTC_FLAGS "-Wno-simple_bus_reg")
115 .. _dt-outputs:
124    Don't include the header files directly. :ref:`dt-from-c` explains
129    input to :file:`gen_defines.py` and used to create :file:`zephyr.dts` and