Lines Matching refs:nodes

16 The cpu nodes (bindings defined in [1]) represent the devices that
22 For instance in a system where CPUs support SMT, "cpu" nodes represent all
24 In systems where SMT is not supported "cpu" nodes represent all cores present
27 ARM topology bindings allow one to associate cpu nodes with hierarchical groups
29 tree nodes.
39 A topology description containing phandles to cpu nodes that are not compliant
48 nodes are listed.
64 	The cpu-map node's child nodes can be:
66 	- one or more cluster nodes
70 The cpu-map node can only contain three types of child nodes:
78 The nodes describing the CPU topology (cluster/core/thread) can only
84 2.1 - cpu-map child nodes naming convention
87 cpu-map child nodes must follow a naming convention where the node name
89 cluster/core/thread) (where N = {0, 1, ...} is the node number; nodes which
92 cpu-map child nodes which do not share a common parent node can have the same
93 name (ie same number N as other cpu-map child nodes at different device tree
100 Bindings for cluster/cpu/thread nodes are defined as follows:
106 		      clustering and cluster nodes can be contained in parent
107 		      cluster nodes.
112 	A cluster node's child nodes must be:
114 	- one or more cluster nodes; or
115 	- one or more core nodes
123 		     nodes are leaf nodes, otherwise they become containers of
124 		     thread nodes.
130 	Properties for core nodes that are leaf nodes:
139 	child nodes can be:
141 	- one or more thread nodes
148 		     in the core if the system supports SMT. Thread nodes are
149 		     always leaf nodes in the device tree.