Lines Matching refs:node
29 a-node {
30 subnode_nodelabel: a-sub-node {
45 #. A root node: ``/``
46 #. A node named ``a-node``, which is a child of the root node
47 #. A node named ``a-sub-node``, which is a child of ``a-node``
49 .. _dt-node-labels:
51 Nodes can be assigned *node labels*, which are unique shorthands that refer to
52 the labeled node. Above, ``a-sub-node`` has the node label
53 ``subnode_nodelabel``. A node can have zero, one, or multiple node labels. You
54 can use node labels to refer to the node elsewhere in the devicetree.
58 (``/``), and the root node's path is a single slash: ``/``. Otherwise, each
59 node's path is formed by concatenating the node's ancestors' names with the
60 node's own name, separated by slashes. For example, the full path to
61 ``a-sub-node`` is ``/a-node/a-sub-node``.
70 Node ``a-sub-node`` has a property named ``foo``, whose value is a cell with
79 In practice, devicetree nodes usually correspond to some hardware, and the node
90 I2C peripheral nodes would be children of the bus controller node.
115 In practice, properties usually describe or configure the hardware the node
116 represents. For example, an I2C peripheral's node has a property whose value is
119 Here's a tree representing the same example, but with real-world node
126 Node names are at the top of each node with a gray background.
164 parts of node names after an "at" sign (``@``), like ``40003000`` in
166 the ``soc`` node does not have one.
168 In devicetree, unit addresses give a node's address in the
169 address space of its parent node. Here are some example unit addresses for
174 For example, the node named ``i2c@40003000`` represents an I2C controller
179 For example, the child node ``apds9960@39`` of the I2C controller
188 For example, a node named ``memory@2000000`` represents RAM starting at
193 For example, a node named ``flash@8000000`` represents a flash device
212 The node named ``partition@0`` has offset 0 from the start of its flash
214 the node named ``partition@20000`` is 0x8020000.
228 The name of the hardware device the node represents.
241 :ref:`bindings <dt-bindings>` for the node. Device drivers use
276 A string which describes whether the node is enabled.
283 A node is considered enabled if its status property is either ``"okay"`` or
291 Note that a child node is not implicitly disabled when its parent node is
311 which is distinct from the standard :ref:`node label <dt-node-labels>`.
402 You can write a phandle using ``&foo``, where ``foo`` is a :ref:`node label
403 <dt-node-labels>`. Here is an example devicetree fragment:
412 The ``sibling`` property of node ``device@1`` contains three cells, in this order:
414 #. The ``device@0`` node's phandle, which is written here as ``&foo`` since
415 the ``device@0`` node has a node label ``foo``
421 values as *node identifiers*. Node identifiers are covered in more detail in
441 There are two additional ways beyond :ref:`node labels <dt-node-labels>` to
442 refer to a particular node without specifying its entire path: by alias, or by
443 chosen node.
470 Above, ``my-uart`` is an alias for the node with path ``/soc/serial@12340000``.
471 Using its node label ``uart0``, the same node is set as the value of the chosen
472 ``zephyr,console`` node.
479 The ``/chosen`` node's properties are used to configure system- or