16 There are two types of devicetree input files: *devicetree sources* and
30 All Zephyr and application source code files can include and use
503 .. _devicetree-in-out-files:
505 Input and output files
508 This section describes the input and output files shown in the figure at the
514    Devicetree input (green) and output (yellow) files
516 .. _dt-input-files:  argument
518 Input files  argument
521 There are four types of devicetree input files:
528 The devicetree files inside the :file:`zephyr` directory look like this::
539 :file:`BOARD.dts` includes one or more ``.dtsi`` files. These ``.dtsi`` files
541 ``.dtsi`` files. They can also describe other common hardware features shared by
547 subdirectories (:file:`dts/<ARCH>`) contain ``.dtsi`` files for CPUs or SoCs
550 The C preprocessor is run on all devicetree files to expand macro references,
555 also DTS files; the :file:`.overlay` extension is just a convention which makes
565 The build system automatically picks up :file:`.overlay` files stored in
570 The build system combines :file:`BOARD.dts` and any :file:`.overlay` files by
574 ``.dtsi`` files, but the principle is the same for overlays). Putting the
575 contents of the :file:`.overlay` files last allows them to override
578 :ref:`dt-bindings` (which are YAML files) are essentially glue. They describe
583 Zephyr currently uses :file:`dts_fixup.h` files to rename macros in
585 build system looks for fixup files in the :file:`zephyr/boards/` and
586 :file:`zephyr/soc/` directories by default. Fixup files exist for historical
595 create output files from input files. Their sources have extensive
623 Output files  argument
630    Don't include the header files directly. :ref:`dt-from-c` explains
638    The concatenated contents of any :file:`dts_fixup.h` files.