Lines Matching refs:that

15 is a description of hardware that is readable by an operating system
16 so that the operating system doesn't need to hard code details of the
35 incompatible, bindings for i2c busses that came about because the new
60 also added to the PowerPC boot wrapper (arch/powerpc/boot/*) so that
76 The most important thing to understand is that the DT is simply a data
77 structure that describes the hardware.  There is nothing magical about
81 Linux kernel (or any other operating system for that matter).  Using
102 machine during early boot so that it has the opportunity to run
126 claims that it compatible with the OMAP 3450 SoC, and the omap3 family
127 of SoCs in general.  You'll notice that the list is sorted from most
130 Astute readers might point out that the Beagle xM could also claim
147 If one does, then that machine_desc is a candidate for driving the
153 The reasoning behind this scheme is the observation that in the majority
157 require special setup code that is not useful in the generic case.
168 that required special workaround code during early boot, then a new
195 properties define the address and size of an initrd blob.  Note that
213 that supports the board.
228 specific setup that needs to be executed early in the boot process,
323 nodes that don't describe devices (although arguably memory could be
331 The trick is that the kernel starts at the root of the tree and looks
332 for nodes that have a 'compatible' property.  First, it is generally
333 assumed that any node with a 'compatible' property represents a device
334 of some kind, and second, it can be assumed that any node at the root
336 miscellaneous system device that cannot be described any other way.
341 Well, for the way that Linux models devices, just about all bus_types
342 assume that its devices are children of a bus controller.  For
348 device are platform_devices (and amba_devices, but more on that
358 table (yet).  For a board that only needs to register devices,
369 According to that model, a driver could be written that binds to the
376 Actually, it turns out that registering children of some
378 device tree support code reflects that and makes the above example
380 of_device_id table, and any node that matches an entry in that table
393 always be traversed.  However, we pass it in as an argument so that
404 used to represent Primecell devices.  However, the fiddly bit is that