Lines Matching refs:DT

13 The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
19 Structurally, the DT is a tree, or acyclic graph with named nodes, and
41 The DT was originally created by Open Firmware as part of the
53 and 64-bit support, the decision was made to require DT support on all
55 Firmware.  To do this, a DT representation called the Flattened Device
59 Device Tree Binary (dtb) and to modify a dtb at boot time.  DT was
62 existing non-DT aware firmware.
67 out of mainline (nios) have some level of DT support.
76 The most important thing to understand is that the DT is simply a data
90 Linux uses DT data for three major purposes:
97 First and foremost, the kernel will use data in the DT to identify the
180 In most cases, a DT will be the sole method of communicating data from
207 early_init_dt_scan_root() to initialize the DT address space model,
225 thing when using a DT.
229 and .init_irq() is used to set up interrupt handling.  Using a DT
231 If a DT is provided, then both .init_early() and .init_irq() are able
232 to call any of the DT query functions (of_* in include/linux/of*.h) to
235 The most interesting hook in the DT context is .init_machine() which
240 registering it en-masse in .init_machine().  When DT is used, then
242 devices can be obtained by parsing the DT, and allocating device
249 later).  While there is no 'platform device' terminology for the DT,
319 this DT and decide which nodes to create platform_devices for.
345 same hierarchy is also found in the DT, where I2C device nodes only
350 tree.  Therefore, if a DT node is at the root of the tree, then it
364 as platform devices too?  For Linux DT support, the generic behaviour
409 When using the DT, this creates problems for of_platform_populate()