zephyr/doc/build/dts
Marti Bolivar c4b10874eb doc: dts: add missing entry to dts/bindings search path
Since SHIELD_DIRS gets added to DTS_ROOT in dts.cmake, any shield
directories are also places where we look for bindings by default.
This feature is not used in upstream Zephyr, but it is supported,
so document it.

Suggested-by: Jamie McCrae <jamie.mccrae@nordicsemi.no>
Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
2023-01-23 07:16:04 -08:00
..
api doc: dts: touch up api 2023-01-23 07:16:04 -08:00
api-usage.rst doc: dts: touch up api-usage 2023-01-23 07:16:04 -08:00
bindings-intro.rst doc: dts: add missing entry to dts/bindings search path 2023-01-23 07:16:04 -08:00
bindings-syntax.rst doc: dts: add guide to phandles 2023-01-23 07:16:04 -08:00
bindings-upstream.rst doc: dts: document zephyr, prefix for props/compats 2023-01-23 07:16:04 -08:00
bindings.rst doc: dts: split up bindings docs 2023-01-23 07:16:04 -08:00
design.rst doc: dts: clarify a design requirement 2023-01-23 07:16:04 -08:00
dt-vs-kconfig.rst
howtos.rst
index.rst doc: dts: add guide to phandles 2023-01-23 07:16:04 -08:00
intro-input-output.rst doc: dts: split up intro 2023-01-23 07:16:04 -08:00
intro-scope-purpose.rst doc: dts: split up intro 2023-01-23 07:16:04 -08:00
intro-syntax-structure.rst doc: dts: clarify reg format 2023-01-23 07:16:04 -08:00
intro.rst doc: dts: split up intro 2023-01-23 07:16:04 -08:00
macros.bnf
main-example.dts
phandles.rst doc: dts: add guide to phandles 2023-01-23 07:16:04 -08:00
troubleshooting.rst
zephyr-user-node.rst doc: dts: improve zephyr-user-node.rst 2023-01-23 07:16:04 -08:00
zephyr_dt_build_flow.png
zephyr_dt_build_flow.svg
zephyr_dt_i2c_example.png
zephyr_dt_i2c_example.svg
zephyr_dt_i2c_high_level.png
zephyr_dt_i2c_high_level.svg
zephyr_dt_inputs_outputs.svg