Lines Matching refs:node
45 # If the node describes bus hardware, like an SPI bus controller
49 # If the node instead appears as a device on a bus, like an external
66 A free-form description of node hardware goes here. You can put links to
82 This devicetree node would match the above binding:
91 match this node:
99 Each node's ``compatible`` property is tried in order. The first matching
137 In this example, a node with compatible ``"manufacturer,serial"`` must contain
139 integer. Similarly, the node must contain a ``reg`` property.
151 node has a matching binding or not.
186 # it's obligatory for the example node and set 'required: true'.
250 node matches the binding, but does not contain the property.
309 - a path to a node as a phandle path reference or path string
311 ``foo = "/path/to/some/node";``
336 property is missing from the devicetree node.
347 If property ``foo`` is missing in a matching node, then the output will be as
425 my-node {
446 ``child-binding`` can be used when a node has children that all share the same
448 though an explicit ``compatible = ...`` on the child node takes precedence, if
451 Consider a binding for a PWM LED node like this one, where the child nodes are
495 will apply to the ``grandchild`` node in this DTS:
513 If the node is a bus controller, use ``bus:`` in the binding to say what type
524 children of any node matching this binding appear on this type of bus.
543 If the node appears as a device on a bus, use ``on-bus:`` in the binding to say
558 When looking for a binding for a node, the build system checks if the binding
559 for the parent node contains ``bus: <bus type>``. If it does, then only
563 The search repeats for each item in the node's ``compatible`` property, in
570 The sensor node may therefore appear in the devicetree as a child node of
624 Consider a binding for a node whose phandle may appear in a ``phandle-array``
639 my-node {
661 A ``*-names`` (e.g. ``pwm-names``) property can appear on the node as well,