Lines Matching +full:in +full:- +full:tree

1 .\"-
6 .\" Cambridge Computer Laboratory under DARPA/AFRL contract (FA8750-10-C-0237)
10 .\" Redistribution and use in source and binary forms, with or without
15 .\" 2. Redistributions in binary form must reproduce the above copyright
16 .\" notice, this list of conditions and the following disclaimer in the
22 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
26 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
27 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
36 .Nd device tree compiler
43 .Op Fl E Ar [no-]checker_name
52 .Op Fl W Ar [no-]checker_name
58 utility converts between flattened device tree (FDT) representations.
59 It is most commonly used to generate device tree blobs (DTB), the binary
60 representation of an FDT, from device tree sources (DTS), the ASCII text source
63 The binary can be written in two formats, binary and assembly.
64 The binary is identical to the in-memory representation and can be used
66 The assembly format, documented in
71 with the device tree blob compiled in.
74 .Bl -tag -width indent
77 This file can be included in a Makefile and will ensure that the output file
83 .It Fl E Ar [no-]checker_name
86 The full list of checkers is given in
95 Specifies the type of phandle nodes to generate in the output.
98 .Bl -tag -width indent -compact
102 Generate the phandle nodes, as described in the ePAPR specification.
112 .Bl -tag -width indent -compact
114 Device tree blob.
117 Device tree source.
125 .Bl -tag -width indent -compact
127 Assembler source for generating a device tree blob, as described in
130 Device tree blob.
134 Device tree source.
140 Defines a macro, in the form
144 to be used for device tree source files that contain conditional components.
157 This is useful if you are generating a device tree blob for bootloader or
161 The minimum size in bytes of the blob.
164 This is useful for environments where the device tree blob must be modified in
170 This is useful for environments where the device tree blob must be modified in
172 .It Fl W Ar [no-]checker_name
177 Sorts the properties and nodes in the tree.
180 to compare two device tree sources.
192 compilation units, in addition to any labels specified in the source.
195 .Bl -tag -width "dt_strings_start" -compact -offset indent
197 start of the device tree blob.
211 end of the device tree blob.
215 tree.
220 .Fl W Ar no-type-phandle
224 .Bl -tag -width "no-type-phandle" -compact -offset indent
225 .It type-compatible
229 .It type-model
233 .It type-compatible
237 .It cells-attributes
239 .Va #address-cells
241 .Va #size-cells
243 .It deleted-nodes
245 .Va /delete-node/
250 Overlays are a method of patching a base device tree that has been compiled with
260 should be included in the header, following any applicable
261 .Va /dts-v1/\&;
266 nodes in a root.
270 .Va target-path
275 tree when the overlay is applied.
279 node that targets a label in the base FDT using the
281 syntax supported in conventional DTS.
288 Additionally, a path-based version of this syntactic sugar is supported.
289 A root node may target a path in the base FDT using a name of the form
291 A fragment will be generated for the node as it is in the
294 .Va target-path
301 Both conventional overlays and the later-added syntactic sugar are supported.
307 Multiple overlays may be specified, and they will be applied in the order given.
310 .Va /omit-if-no-ref/
312 elsewhere in the device tree.
313 This may be used in more space-constrained environments to remove nodes that may
314 not be applicable to the specific device the tree is being compiled for.
319 and will not be removed from the tree.
323 .Dl "dtc -o blob.S -O asm device.dts"
327 file from the device tree source
334 .Dl "dtc -o - -O dts -I dtb device.dtb"
336 will write the device tree source for the device tree blob
343 .Dl "dtc -@ -O dtb -I dts -o device.dtb device.dts"
347 file from the device tree source
353 .Dl "dtc -@ -O dtb -I dts -o device_overlay.dtbo device_overlay.dts"
357 file, using the standard extension for a device tree overlay, from the device
358 tree source
363 directive in
366 metadata required in overlays.
368 This utility is intended to be compatible with the device tree compiler
380 This builds a tree from a Linux
381 .Pa /proc/device-tree ,
382 a file system hierarchy not found in
387 This tool supports the warnings described in the
393 The device tree formats understood by this tool conform to the Power.org
396 except as noted in the
401 .Bl -bullet -compact
403 The target of cross references is defined to be a node name in the
404 specification, but is in fact a label.
409 It must appear in the top level of a file, and imports a new root definition.
412 All nodes that are present in the second but not the first are imported.
413 Any that appear in both are recursively merged, with properties from the second
417 A dtc tool first appeared in
419 This version of the tool first appeared in
431 The device tree compiler does not yet support the following features:
433 .Bl -bullet -compact
435 Labels in the middle of property values.
436 This is only useful in the assembly output, and only vaguely useful there, so
444 The current version performs a very limited set of semantic checks on the tree.
445 This will be improved in future versions.