Lines Matching full:tree
21 2) Device tree generalities
22 3) Device tree "structure" block
23 4) Device tree "strings" block
25 III - Required content of the device tree
38 IV - "dtc", the device tree compiler
65 small device tree, though it is encouraged
93 - Add a chapter about the device-tree
95 the tree that can be "compiled" by dtc.
105 - Add some definitions of interrupt tree (simple/complex)
127 but no new board support will be accepted in the main tree that
134 the presence of a device-tree whose format is defined after Open
136 to embedded board vendors, the kernel doesn't require the device-tree
170 b) Entry with a flattened device-tree block. Firmware loads the
171 physical address of the flattened device tree block (dtb) into r2,
177 r1 : Valid machine type number. When using a device tree,
181 r2 : physical pointer to the device-tree block
182 (defined in chapter II) in RAM. Device tree can be located
186 The kernel will differentiate between ATAGS and device tree booting by
188 device tree block magic value (0xd00dfeed) or the ATAG_CORE value at
211 extract the device-tree and other information from open
212 firmware and build a flattened device-tree as described
218 b) Direct entry with a flattened device-tree block. This entry
229 r3 : physical pointer to the device-tree block
249 given platform based on the content of the device-tree. Thus, you
277 The physical pointer to the device-tree block (defined in chapter II)
283 This device-tree is used as an extension to the "boot page". As such it
293 This chapter defines the actual format of the flattened device-tree
297 which will generate a flattened device-tree from the Open Firmware
338 /* Definitions used by the flattened device tree */
351 from the physical base address of the device tree block.
356 device-tree block header. It contains the value 0xd00dfeed and is
364 the device-tree structure, strings, and the memory reserve map.
369 of the "structure" part the device tree. (see 2) device tree)
374 of the "strings" part of the device-tree
385 boot for things like un-flattening the device-tree, allocating an
402 "compact" format for the tree itself that is however not backward
406 adjustments to a device tree based on probed information). You
417 should put a 1 in this field if you generate a device tree of
418 version 1 to 3, or 16 if you generate a tree of version 16 or 17
427 the device-tree corresponding to the CPU calling the kernel entry
429 device-tree contents)
434 gives the size of the "strings" section of the device tree (which
440 the size of the "structure" section of the device tree (which
458 | device-tree structure |
464 | device-tree strings |
476 2) Device tree generalities
479 This device-tree itself is separated in two different blocks, a
483 First, let's quickly describe the device-tree concept before detailing
488 The device-tree layout is strongly inherited from the definition of
489 the Open Firmware IEEE 1275 device-tree. It's basically a tree of
493 It is a tree, so each node has one and only one parent except for the
508 the device-tree structure. It is typically used to represent "path" in
509 the device-tree. More details about the actual format of these will be
515 the node unit name at a given level of the tree. Nodes with no notion
539 if the flattened device tree is used directly. An example of a node
541 interrupt tree which will be described in a further version of this
550 Here is an example of a simple device-tree. In this example, an "o"
556 only meant to give you a idea of what a device-tree looks like. I have
558 aren't necessary in order to give you a better idea of what the tree
561 / o device-tree
562 |- name = "device-tree"
594 This tree is almost a minimal tree. It pretty much contains the
608 3) Device tree "structure" block
610 The structure of the device tree is a linearized tree structure. The
614 bit value. The tree has to be "finished" with a OF_DT_END token
643 manipulating a flattened tree must take care to preserve this
646 4) Device tree "strings" block
651 concatenated together. The device-tree property definitions in the
656 III - Required content of the device tree
660 to a flattened device-tree. If your platform uses a real
665 set the platform number. However, when using the flattened device-tree
674 documentations. If you choose to describe a bus with the device-tree
677 device or bus to be described by the device tree.
688 like the example tree given above, then an address and a size are both
805 PCI binding to Open Firmware, and your interrupt tree as documented
806 in OF interrupt tree specification.
1020 IV - "dtc", the device tree compiler
1028 resulting device-tree "blobs" have not yet been validated with the
1034 dtc basically takes a device-tree in a given format and outputs a
1035 device-tree in another format. The currently supported formats are:
1040 - "dtb": "blob" format, that is a flattened device-tree block
1044 "source" for a device-tree. The format is defined later in this
1047 output of /proc/device-tree, that is nodes are directories and
1056 sourced by gas to generate a device-tree "blob". That file can
1071 Additionally, dtc performs various sanity checks on the tree, like the
1080 The above is the "device-tree" definition. It's the only statement
1114 structure of the tree.
1125 you link the device-tree with), label or path instead of numeric value
1143 - The bootloader may want to be able to use the device-tree itself
1147 flattened format, or the bootloader has its own internal tree
1149 re-flattens the tree when booting the kernel. The former is a bit
1151 more code to handle the tree structure. Note that the structure
1158 directly from the flattened tree format can be found in the kernel
1178 implementations define as complete a flat-device-tree as possible to
1197 specifications for the format of the device tree node. All SOC child
1213 That directory will expand as device tree support is added to more and
1220 The device tree represents the buses and devices of a hardware
1224 In addition, a logical 'interrupt tree' exists which represents the
1227 The interrupt tree model is fully described in the
1246 interrupt tree. The root of an interrupt domain specifies in
1265 the interrupt tree. The value of interrupt-parent is the