Lines Matching refs:node
16 The usual way to get a phandle for a devicetree node is from one of its node
22 lbl_a: node-1 {};
23 lbl_b: lbl_c: node-2 {};
28 - ``/node-1`` as ``&lbl_a``
29 - ``/node-2`` as either ``&lbl_b`` or ``&lbl_c``
44 One node: phandle type
47 You can use phandles to refer to ``node-b`` from ``node-a``, where ``node-b``
48 is related to ``node-a`` in some way.
50 One common example is when ``node-a`` represents some hardware that
51 generates an interrupt, and ``node-b`` represents the interrupt
57 node_b: node-b {
61 node-a {
77 phandles, each of which "points" to a node containing information related to
93 "owned" by some other node.
106 another node along with additional metadata about the resource.
116 node {
153 In the devicetree, there will be a node that represents the GPIO controller
155 developed in hardware. Therefore, there is no single node in the devicetree
167 "group" in its value. ``&gpioX`` is the phandle for the GPIO controller node
173 The device driver handling the ``my-external-ic`` node can then use the
217 node {
240 foo: node@1000 {
244 bar: node@2000 {
255 A single node can also have different numbers of cells in different specifier
260 foo: node@1000 {
271 node {
276 This flexibility allows you to have a node that manages multiple different
277 kinds of resources at the same time. The node describes the amount of metadata