Lines Matching refs:binding

22    # A high level description of the device the binding applies to:
34    # Used to match nodes to this binding:
39      # binding's nodes need to satisfy go here.
41    child-binding:
42      # You can constrain the children of the nodes matching this binding
74 This key is used to match nodes to this binding as described in
75 :ref:`dt-binding-compat`. It should look like this in a binding file:
82 This devicetree node would match the above binding:
90 Assuming no binding has ``compatible: "manufacturer,device-v2"``, it would also
100 binding is used. The :ref:`on-bus: <dt-bindings-on-bus>` key can be used to
103 If more than one binding for a compatible is found, an error is raised.
119 The ``properties:`` key describes properties that nodes which match the binding
120 contain. For example, a binding for a UART peripheral might look something like
145 key for the matching binding. Properties not mentioned in the binding are
151 node has a matching binding or not.
250 node matches the binding, but does not contain the property.
338 For example, with this binding fragment:
364 a property value in DTS is not in the ``enum:`` list in the binding, an error
443 Child-binding
446 ``child-binding`` can be used when a node has children that all share the same
447 properties. Each child gets the contents of ``child-binding`` as its binding,
449 a binding is found for it.
451 Consider a binding for a PWM LED node like this one, where the child nodes are
468 The binding would look like this:
474    child-binding:
482 ``child-binding`` also works recursively. For example, this binding:
488    child-binding:
489      child-binding:
513 If the node is a bus controller, use ``bus:`` in the binding to say what type
514 of bus. For example, a binding for a SPI peripheral on an SoC would look like
523 The presence of this key in the binding informs the build system that the
524 children of any node matching this binding appear on this type of bus.
530 in the binding can have a list as value:
543 If the node appears as a device on a bus, use ``on-bus:`` in the binding to say
546 For example, a binding for an external SPI memory chip should include this line:
552 And a binding for an I2C based temperature sensor should include this line:
558 When looking for a binding for a node, the build system checks if the binding
595 You can write two separate binding files which match these individual sensor
613 for a binding for ``sensor@0``.
620 This section documents how to name the cells in a specifier within a binding.
624 Consider a binding for a node whose phandle may appear in a ``phandle-array``
689 included into this binding.
692 merge. The build system will check that the resulting merged binding is
693 well-formed. It is allowed to include at any level, including ``child-binding``,
701    child-binding:
705 It is an error if a key appears with a different value in a binding and in a
706 file it includes, with one exception: a binding can have ``required: true`` for
716 definitions for many common properties. When writing a new binding, it is a
782 Finally, you can filter from a child binding like this:
788        child-binding: