Lines Matching refs:tree
22 2) Device tree generalities
23 3) Device tree "structure" block
24 4) Device tree "strings" block
26 III - Required content of the device tree
39 IV - "dtc", the device tree compiler
68 small device tree, though it is encouraged
96 - Add a chapter about the device-tree
98 the tree that can be "compiled" by dtc.
108 - Add some definitions of interrupt tree (simple/complex)
130 but no new board support will be accepted in the main tree that
137 the presence of a device-tree whose format is defined after Open
139 to embedded board vendors, the kernel doesn't require the device-tree
173 b) Entry with a flattened device-tree block. Firmware loads the
174 physical address of the flattened device tree block (dtb) into r2,
180 r1 : Valid machine type number. When using a device tree,
184 r2 : physical pointer to the device-tree block
185 (defined in chapter II) in RAM. Device tree can be located
189 The kernel will differentiate between ATAGS and device tree booting by
191 device tree block magic value (0xd00dfeed) or the ATAG_CORE value at
214 extract the device-tree and other information from open
215 firmware and build a flattened device-tree as described
221 b) Direct entry with a flattened device-tree block. This entry
232 r3 : physical pointer to the device-tree block
252 given platform based on the content of the device-tree. Thus, you
280 The physical pointer to the device-tree block (defined in chapter II)
286 This device-tree is used as an extension to the "boot page". As such it
307 a2 : Physical pointer to the device tree block (defined in chapter
308 II) in RAM. The device tree can be located anywhere in the first
323 This chapter defines the actual format of the flattened device-tree
327 which will generate a flattened device-tree from the Open Firmware
368 /* Definitions used by the flattened device tree */
381 from the physical base address of the device tree block.
386 device-tree block header. It contains the value 0xd00dfeed and is
394 the device-tree structure, strings, and the memory reserve map.
399 of the "structure" part the device tree. (see 2) device tree)
404 of the "strings" part of the device-tree
415 boot for things like un-flattening the device-tree, allocating an
432 "compact" format for the tree itself that is however not backward
436 adjustments to a device tree based on probed information). You
447 should put a 1 in this field if you generate a device tree of
448 version 1 to 3, or 16 if you generate a tree of version 16 or 17
457 the device-tree corresponding to the CPU calling the kernel entry
459 device-tree contents)
464 gives the size of the "strings" section of the device tree (which
470 the size of the "structure" section of the device tree (which
488 | device-tree structure |
494 | device-tree strings |
506 2) Device tree generalities
509 This device-tree itself is separated in two different blocks, a
513 First, let's quickly describe the device-tree concept before detailing
518 The device-tree layout is strongly inherited from the definition of
519 the Open Firmware IEEE 1275 device-tree. It's basically a tree of
523 It is a tree, so each node has one and only one parent except for the
538 the device-tree structure. It is typically used to represent "path" in
539 the device-tree. More details about the actual format of these will be
545 the node unit name at a given level of the tree. Nodes with no notion
569 if the flattened device tree is used directly. An example of a node
571 interrupt tree which will be described in a further version of this
580 Here is an example of a simple device-tree. In this example, an "o"
587 you a idea of what a device-tree looks like. I have purposefully kept
589 order to give you a better idea of what the tree looks like in
592 / o device-tree
593 |- name = "device-tree"
625 This tree is almost a minimal tree. It pretty much contains the
639 3) Device tree "structure" block
641 The structure of the device tree is a linearized tree structure. The
645 bit value. The tree has to be "finished" with a OF_DT_END token
674 manipulating a flattened tree must take care to preserve this
677 4) Device tree "strings" block
682 concatenated together. The device-tree property definitions in the
687 III - Required content of the device tree
691 to a flattened device-tree. If your platform uses a real
696 set the platform number. However, when using the flattened device-tree
705 documentations. If you choose to describe a bus with the device-tree
708 device or bus to be described by the device tree.
719 like the example tree given above, then an address and a size are both
836 PCI binding to Open Firmware, and your interrupt tree as documented
837 in OF interrupt tree specification.
1055 IV - "dtc", the device tree compiler
1063 resulting device-tree "blobs" have not yet been validated with the
1069 dtc basically takes a device-tree in a given format and outputs a
1070 device-tree in another format. The currently supported formats are:
1075 - "dtb": "blob" format, that is a flattened device-tree block
1079 "source" for a device-tree. The format is defined later in this
1082 output of /proc/device-tree, that is nodes are directories and
1091 sourced by gas to generate a device-tree "blob". That file can
1106 Additionally, dtc performs various sanity checks on the tree, like the
1115 The above is the "device-tree" definition. It's the only statement
1149 structure of the tree.
1160 you link the device-tree with), label or path instead of numeric value
1178 - The bootloader may want to be able to use the device-tree itself
1182 flattened format, or the bootloader has its own internal tree
1184 re-flattens the tree when booting the kernel. The former is a bit
1186 more code to handle the tree structure. Note that the structure
1193 directly from the flattened tree format can be found in the kernel
1213 implementations define as complete a flat-device-tree as possible to
1232 specifications for the format of the device tree node. All SOC child
1248 That directory will expand as device tree support is added to more and
1255 The device tree represents the buses and devices of a hardware
1259 In addition, a logical 'interrupt tree' exists which represents the
1262 The interrupt tree model is fully described in the
1281 interrupt tree. The root of an interrupt domain specifies in
1300 the interrupt tree. The value of interrupt-parent is the
1392 structure of a memory-mapped bus whose device tree parent can be accessed