Lines Matching full:bindings

1 .. _dt-bindings-file-syntax:
3 Devicetree bindings syntax
6 This page documents the syntax of Zephyr's bindings format. Zephyr bindings
7 files are YAML files. A :ref:`simple example <dt-bindings-simple-example>` was
17 The top level of a bindings file maps keys to values. The top-level keys look
27 and are encouraged for complex bindings.
31 # You can include definitions from other bindings using this syntax:
52 # bindings.
61 .. _dt-bindings-description:
69 .. _dt-bindings-compatible:
100 binding is used. The :ref:`on-bus: <dt-bindings-on-bus>` key can be used to
106 :zephyr_file:`dts/bindings/vendor-prefixes.txt` for a list of accepted vendor
109 Some bindings apply to a generic class of devices which do not have a specific
114 .. _dt-bindings-properties:
141 The build system uses bindings to generate C macros for devicetree properties
175 .. _dt-bindings-example-properties:
330 .. _dt-bindings-default:
353 For rules related to ``default`` in upstream Zephyr bindings, see
354 :ref:`dt-bindings-default-rules`.
356 See :ref:`dt-bindings-example-properties` for examples. Putting ``default:`` on
357 any property type besides those used in :ref:`dt-bindings-example-properties`
365 is raised. See :ref:`dt-bindings-example-properties` for examples.
374 .. _dt-bindings-specifier-space:
441 .. _dt-bindings-child:
508 .. _dt-bindings-bus:
526 This in turn influences the way ``on-bus:`` is used to match bindings for the
538 .. _dt-bindings-on-bus:
560 bindings with a matching ``on-bus: <bus type>`` and bindings without an
561 explicit ``on-bus`` are considered. Bindings with an explicit ``on-bus: <bus
562 type>`` are searched for first, before bindings without an explicit ``on-bus``.
566 This feature allows the same device to have different bindings depending on
615 .. _dt-bindings-cells:
643 The bindings for compatible ``"foo,pwm"`` and ``"bar,pwm"`` must give a name to
671 .. _dt-bindings-include:
676 Bindings can include other files, which can be used to share common property
677 definitions between bindings. Use the ``include:`` key for this. Its value is
688 :ref:`dt-where-bindings-are-located` for the search process), it will be
691 Included files are merged into bindings with a simple recursive dictionary
707 a :ref:`property definition <dt-bindings-properties>` for which the included
709 bindings to strengthen requirements from included files.
715 The file :zephyr_file:`base.yaml <dts/bindings/base/base.yaml>` contains