Lines Matching full:devicetree
78 Devicetree bindings. The MAINTAINERS file entry should list new
93 Devicetree ABI Stability
97 document the ABI between the devicetree and the kernel.
98 Please read Documentation/devicetree/bindings/ABI.rst.
100 If changes are being made to a devicetree that are incompatible with old
101 kernels, the devicetree patch should not be applied until the driver is, or an
110 A common problem is synchronizing changes between device drivers and devicetree
115 corresponding change to the devicetree binding description, to ensure they are
116 in fact compatible. This means that the devicetree branch can end up causing
117 warnings in the "make dtbs_check" step. If a devicetree change depends on
127 * Use literal values in the devicetree file in place of macros even when a
131 * Defer the devicetree changes to a release after the binding and driver have
135 both the driver change and the devicetree changes
137 * Add duplicate defines in the devicetree file guarded by an #ifndef section,
140 Devicetree Naming Convention
143 The general naming scheme for devicetree files is as follows. The aspects of a
159 Validating Devicetree Files
162 ``make dtbs_check`` can be used to validate that devicetree files are compliant
164 "Running checks" of Documentation/devicetree/bindings/writing-schema.rst for
170 If in any doubt about a devicetree change, reach out to the devicetree
177 submaintainers will do the same. Driver, defconfig and devicetree changes should
191 SoC tree. An example here would be one branch for devicetree warning fixes, one