Lines Matching full:bindings
1 .. _dt-writing-bindings:
3 Rules for upstream bindings
6 This section includes general rules for writing bindings that you want to
8 for bindings you don't intend to contribute to the Zephyr Project, but it's a
18 Always check for existing bindings
29 :file:`Documentation/devicetree/bindings` in `Linus's tree`_ for existing
30 bindings and the `Linux devicetree documentation`_ for more information.
44 Wherever possible, when writing Devicetree bindings for Zephyr, try to follow
48 https://docs.kernel.org/devicetree/bindings/writing-bindings.html
53 Bindings which match a compatible must have file names based on the compatible.
63 All recommendations in :ref:`dt-bindings-default` are requirements when
114 :zephyr_file:`dts/bindings/vendor-prefixes.txt`, you must use that vendor
123 - Do not submit additions to Zephyr's :file:`dts/bindings/vendor-prefixes.txt`
128 For custom bindings, you can add a custom
129 :file:`dts/bindings/vendor-prefixes.txt` file to any directory in your
132 own bindings or devicetrees.
141 .. _dt-bindings-default-rules:
211 # of the description. This won't be shown in the bindings index.
223 - Zephyr-specific extensions to bindings we share with upstream Linux. One
225 controllers defined in :zephyr_file:`dts/bindings/adc/adc-controller.yaml`.
234 we do allow some software configuration in Zephyr's devicetree bindings, as