mirror of
https://github.com/zephyrproject-rtos/zephyr
synced 2025-09-01 19:43:35 +00:00
3a2417443f
Add a page describing the high-level design goals for how Zephyr should use DT, with examples and counter-examples from current practice. Add a TBD section for code generation. It's not clear (to me at least) where the discussion on that has landed. Signed-off-by: Martí Bolívar <marti.bolivar@nordicsemi.no>
28 lines
659 B
ReStructuredText
28 lines
659 B
ReStructuredText
.. _devicetree:
|
|
|
|
Devicetree
|
|
##########
|
|
|
|
A *devicetree* is a hierarchical data structure which describes hardware\
|
|
[#dt_spelling]_. The `Devicetree specification`_ fully defines its source and
|
|
binary representations. Zephyr uses devicetree to describe the hardware
|
|
available on its :ref:`boards`, as well as that hardware's initial
|
|
configuration.
|
|
|
|
.. _Devicetree specification: https://www.devicetree.org/
|
|
|
|
.. toctree::
|
|
:maxdepth: 2
|
|
|
|
intro.rst
|
|
design.rst
|
|
bindings.rst
|
|
macros.rst
|
|
howtos.rst
|
|
dt-vs-kconfig.rst
|
|
|
|
.. rubric:: Footnotes
|
|
|
|
.. [#dt_spelling] Note that "devicetree" (without spaces) is preferred to
|
|
"device tree".
|