Lines Matching +full:dt +full:- +full:binding

1 .. SPDX-License-Identifier: GPL-2.0
4 Submitting Devicetree (DT) binding patches
11      Documentation/process/submitting-patches.rst applies.
13   1) The Documentation/ and include/dt-bindings/ portion of the patch should
14      be a separate patch. The preferred subject prefix for binding patches is::
16        "dt-bindings: <binding dir>: ..."
20      docs. Repeating "binding" again should also be avoided.
22   2) DT binding files are written in DT schema format using json-schema
23      vocabulary and YAML file format. The DT binding files must pass validation
28      See Documentation/devicetree/bindings/writing-schema.rst for more details
31   3) DT binding files should be dual licensed. The preferred license tag is
32      (GPL-2.0-only OR BSD-2-Clause).
38      and Cc: the DT maintainers. Use scripts/get_maintainer.pl to identify
39      all of the DT maintainers.
42      the code implementing the binding.
45      previously documented in the corresponding DT binding text file
50      ("checkpatch: add DT compatible string documentation checks"). ]
55          - compatible: Must contain '"nvidia,<chip>-pcie",
56            "nvidia,tegra20-pcie"' where <chip> is tegra30, tegra132, ...
63      string that is matched by the driver (as in the "nvidia,tegra20-pcie"
73   1) If you aren't comfortable reviewing a given binding, reply to it and ask
78      binding, and it hasn't received an Acked-by from the devicetree
84   3) For a series going though multiple trees, the binding patch should be
85      kept with the driver using the binding.