Lines Matching refs:nodes
20 For instance in a system where CPUs support SMT, "cpu" nodes represent all
22 In systems where SMT is not supported "cpu" nodes represent all cores present
25 CPU topology bindings allow one to associate cpu nodes with hierarchical groups
27 tree nodes.
32 The cpu nodes, as per bindings defined in [4], represent the devices that
35 A topology description containing phandles to cpu nodes that are not compliant
44 nodes are listed.
60 The cpu-map node's child nodes can be:
62 - one or more cluster nodes or
63 - one or more socket nodes in a multi-socket system
67 The cpu-map node can only contain 4 types of child nodes:
76 The nodes describing the CPU topology (socket/cluster/core/thread) can
82 2.1 - cpu-map child nodes naming convention
85 cpu-map child nodes must follow a naming convention where the node name
87 (ie socket/cluster/core/thread) (where N = {0, 1, ...} is the node number; nodes
90 cpu-map child nodes which do not share a common parent node can have the same
91 name (ie same number N as other cpu-map child nodes at different device tree
98 Bindings for socket/cluster/cpu/thread nodes are defined as follows:
105 The association of sockets and NUMA nodes is beyond
114 A socket node's child nodes must be one or more cluster nodes.
123 nodes can be contained in parent cluster nodes.
128 A cluster node's child nodes must be:
130 - one or more cluster nodes; or
131 - one or more core nodes
139 nodes are leaf nodes, otherwise they become containers of
140 thread nodes.
146 Properties for core nodes that are leaf nodes:
155 child nodes can be:
157 - one or more thread nodes
164 in the core if the system supports SMT. Thread nodes are
165 always leaf nodes in the device tree.