| /rk3399_rockchip-uboot/scripts/dtc/ |
| H A D | fstree.c | 31 struct node *tree; in read_fstree() local
37 tree = build_node(NULL, NULL); in read_fstree()
64 add_property(tree, prop); in read_fstree()
72 add_child(tree, newchild); in read_fstree()
79 return tree; in read_fstree()
84 struct node *tree; in dt_from_fs() local
86 tree = read_fstree(dirname); in dt_from_fs()
87 tree = name_node(tree, ""); in dt_from_fs()
89 return build_dt_info(DTSF_V1, NULL, tree, guess_boot_cpuid(tree)); in dt_from_fs()
|
| H A D | dtc.c | 44 static void fill_fullpaths(struct node *tree, const char *prefix) in fill_fullpaths() argument
49 tree->fullpath = join_path(prefix, tree->name); in fill_fullpaths()
51 unit = strchr(tree->name, '@'); in fill_fullpaths()
53 tree->basenamelen = unit - tree->name; in fill_fullpaths()
55 tree->basenamelen = strlen(tree->name); in fill_fullpaths()
57 for_each_child(tree, child) in fill_fullpaths()
58 fill_fullpaths(child, tree->fullpath); in fill_fullpaths()
|
| H A D | livetree.c | 379 struct node *tree, uint32_t boot_cpuid_phys) in build_dt_info() argument
386 dti->dt = tree; in build_dt_info()
427 struct property *get_property_by_label(struct node *tree, const char *label, in get_property_by_label() argument
433 *node = tree; in get_property_by_label()
435 for_each_property(tree, prop) { in get_property_by_label()
443 for_each_child(tree, c) { in get_property_by_label()
453 struct marker *get_marker_label(struct node *tree, const char *label, in get_marker_label() argument
460 *node = tree; in get_marker_label()
462 for_each_property(tree, p) { in get_marker_label()
470 for_each_child(tree, c) { in get_marker_label()
[all …]
|
| H A D | dtc.h | 221 struct property *get_property_by_label(struct node *tree, const char *label,
223 struct marker *get_marker_label(struct node *tree, const char *label,
226 struct node *get_node_by_path(struct node *tree, const char *path);
227 struct node *get_node_by_label(struct node *tree, const char *label);
228 struct node *get_node_by_phandle(struct node *tree, cell_t phandle);
229 struct node *get_node_by_ref(struct node *tree, const char *ref);
232 uint32_t guess_boot_cpuid(struct node *tree);
265 struct node *tree, uint32_t boot_cpuid_phys);
|
| H A D | treesource.c | 236 static void write_tree_source_node(FILE *f, struct node *tree, int level) in write_tree_source_node() argument
243 for_each_label(tree->labels, l) in write_tree_source_node()
245 if (tree->name && (*tree->name)) in write_tree_source_node()
246 fprintf(f, "%s {\n", tree->name); in write_tree_source_node()
250 for_each_property(tree, prop) { in write_tree_source_node()
257 for_each_child(tree, child) { in write_tree_source_node()
|
| H A D | flattree.c | 250 static void flatten_tree(struct node *tree, struct emitter *emit, in flatten_tree() argument
258 if (tree->deleted) in flatten_tree()
261 emit->beginnode(etarget, tree->labels); in flatten_tree()
264 emit->string(etarget, tree->fullpath, 0); in flatten_tree()
266 emit->string(etarget, tree->name, 0); in flatten_tree()
270 for_each_property(tree, prop) { in flatten_tree()
291 emit->cell(etarget, tree->basenamelen+1); in flatten_tree()
294 if ((vi->flags & FTF_VARALIGN) && ((tree->basenamelen+1) >= 8)) in flatten_tree()
297 emit->string(etarget, tree->name, tree->basenamelen); in flatten_tree()
301 for_each_child(tree, child) { in flatten_tree()
[all …]
|
| /rk3399_rockchip-uboot/lib/zlib/ |
| H A D | trees.c | 145 local void pqdownheap OF((deflate_state *s, ct_data *tree, int k));
147 local void gen_codes OF((ct_data *tree, int max_code, ushf *bl_count));
149 local void scan_tree OF((deflate_state *s, ct_data *tree, int max_code));
150 local void send_tree OF((deflate_state *s, ct_data *tree, int max_code));
168 # define send_code(s, c, tree) send_bits(s, tree[c].Code, tree[c].Len) argument
172 # define send_code(s, c, tree) \ argument
174 send_bits(s, tree[c].Code, tree[c].Len); }
438 #define pqremove(s, tree, top) \ argument
442 pqdownheap(s, tree, SMALLEST); \
449 #define smaller(tree, n, m, depth) \ argument
[all …]
|
| /rk3399_rockchip-uboot/doc/driver-model/ |
| H A D | livetree.txt | 8 Traditionally U-Boot has used a 'flat' device tree. This means that it
9 reads directly from the device tree binary structure. It is called a flat
10 device tree because nodes are listed one after the other, with the
13 This document describes U-Boot's support for a 'live' device tree, meaning
14 that the tree is loaded into a hierarchical data structure within U-Boot.
20 The flat device tree has several advantages:
22 - it is the format produced by the device tree compiler, so no translation
30 However the flat device tree does have some limitations. Adding new
32 The overall tree has a fixed maximum size so sometimes the tree must be
34 properties or nodes, scanning the tree can be slow. For example, finding
[all …]
|
| H A D | fdt-fixup.txt | 1 Pre-relocation device tree manipulation
32 device tree overlay mechanism: There exists one "base" device tree, which
35 boards is then detected, and the corresponding device tree overlays are applied
42 In the U-Boot boot loader, support for device tree overlays has recently been
43 integrated, and is used on some boards to alter the device tree that is later
44 passed to Linux. But since U-Boot's driver model, which is device tree-based as
46 device tree starts cropping up in U-Boot itself as well.
48 An additional problem with the device tree in U-Boot is that it is read-only,
49 and the current mechanisms don't allow easy manipulation of the device tree
51 tree (at least after the relocation) would greatly simplify the solution of
[all …]
|
| H A D | of-plat.txt | 8 Device tree is the standard configuration method in U-Boot. It is used to
12 The overhead of adding device tree access to U-Boot is fairly modest,
14 that in most cases it is best to use device tree for configuration.
19 case the overhead of device tree access may be too great.
23 bypasses the use of device tree completely, effectively creating a parallel
27 device tree contents into C code which can be compiled into the SPL binary.
42 - Device tree does not describe data types. But the C code must define a
48 in the device tree file.
51 the naming in the device tree, which may result in C identifiers that
56 the code less robust in the face of device-tree changes. It also
[all …]
|
| H A D | serial-howto.txt | 35 This may be a good time to move your board to use device tree also. Mostly
39 - add your device tree files to arch/<arch>/dts
41 - Add stdout-path to your /chosen device tree node if it is not already there
43 - Your drivers can now use device tree
44 - For device tree in SPL, define CONFIG_SPL_OF_CONTROL
|
| H A D | i2c-howto.txt | 47 This may be a good time to move your board to use device tree also. Mostly
51 - add your device tree files to arch/<arch>/dts
53 - Add stdout-path to your /chosen device tree node if it is not already there
55 - Your drivers can now use device tree
56 - For device tree in SPL, define CONFIG_SPL_OF_CONTROL
|
| H A D | pci-info.txt | 10 tree file will point to the correct device:
24 tree.
31 After probing a bus, the available devices will appear in the device tree
37 PCI devices can appear in the flattened device tree. If they do this serves to
95 device are on the PCI bus. Like other devices in the device tree, if we want
99 If PCI devices are not listed in the device tree, U_BOOT_PCI_DEVICE can be used
100 to specify the driver to use for the device. The device tree takes precedence
102 DM_FLAG_PRE_RELOC will be bound before relocation. If neither device tree nor
111 is no real PCI bus. This works by looking in the device tree node for a
|
| /rk3399_rockchip-uboot/doc/ |
| H A D | README.marvell | 11 # sudo apt-get install device-tree-compiler
31 5. Configure the device-tree and build the U-Boot image:
33 Compile u-boot and set the required device-tree using:
40 By default, u-boot is compiled with armada-8040-db device-tree.
41 Using A80x0 device-tree on A70x0 might break the device.
42 In order to prevent this, the required device-tree MUST be set during compilation.
43 All device-tree files are located in ./arch/arm/dts/ folder.
|
| H A D | README.fdt-control | 11 device tree (fdt). U-Boot configuration has traditionally been done
15 tree (fdt). This is the approach recently taken by the ARM Linux kernel
28 The dts directory contains a Makefile for building the device tree blob
32 the features of each board in the device tree file, and have a single
61 To use this feature you will need to get the device tree compiler here:
110 to set the filename of the device tree source. Then put your device tree
115 This should include your CPU or SOC's device tree file, placed in
131 tree binary.
134 device tree at runtime, for example if an earlier bootloader stage creates
143 To use a device tree file that you have compiled yourself, pass
|
| H A D | README.fdt-overlays | 10 https://git.kernel.org/pub/scm/utils/dtc/dtc.git/tree/Documentation/dt-object-internal.txt
75 1. Figure out where to place both the base device tree blob and the
76 overlay. Make sure you have enough space to grow the base tree without
87 3. Set it as the working fdt tree.
|
| /rk3399_rockchip-uboot/dts/ |
| H A D | Kconfig | 30 via a flattened device tree.
44 U-Boot's device tree (e.g. to delete device from it). This option
54 Some boards use device tree in U-Boot but only have 4KB of SRAM
55 which is not enough to support device tree. Enable this option to
72 Some boards use device tree in U-Boot but only have 4KB of SRAM
73 which is not enough to support device tree. Enable this option to
77 bool "Enable use of a live tree"
80 Normally U-Boot uses a flat device tree which saves space and
81 avoids the need to unpack the tree before use. However a flat
82 tree does not support modifcation from within U-Boot since it
[all …]
|
| /rk3399_rockchip-uboot/board/qualcomm/dragonboard410c/ |
| H A D | readme.txt | 17 6) Generate qualcomm device tree table with dtbTool [1]
46 [1] To boot any kernel image, Little Kernel requires valid device tree for the
47 platform it runs on. dtbTool creates device tree table that Little Kernel scans.
48 Later on proper device tree is passed to next boot stage.
49 Full device tree is not required to boot u-boot. Enough would be:
|
| /rk3399_rockchip-uboot/drivers/pinctrl/nxp/ |
| H A D | Kconfig | 13 i.MX53. This feature depends on device tree
27 i.MX6DQ/SL/SX/UL/DQP. This feature depends on device tree
41 i.MX7D. This feature depends on device tree
55 This feature depends on device tree configuration. This driver
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/exynos/ |
| H A D | soc.txt | 3 The "cpu-model" property is a non-standard extension for the device tree root
8 to the device tree file name. The same name is generated in U-Boot, so the new
|
| /rk3399_rockchip-uboot/drivers/pinctrl/ |
| H A D | Kconfig | 19 This provides Linux-compatible device tree interface for the pinctrl
20 subsystem. This feature depends on device tree configuration because
21 it parses a device tree to look for the pinctrl device which the
53 The driver is typically controlled by the device tree.
111 driver or in the device tree. If this is acceptable and you need
113 enable this option. You will need to enable device tree in SPL
139 The driver is controlled by a device tree node which contains
187 SoCs. This driver is controlled by a device tree node which
196 The driver is controlled by a device tree node which contains both
207 The driver is controlled by a device tree node which contains both
[all …]
|
| /rk3399_rockchip-uboot/scripts/dtc/pylibfdt/ |
| H A D | libfdt.i_shipped | 113 """Device tree class, supporting all operations
115 The Fdt object is created is created from a device tree binary file,
225 tree format)
264 """Return the total size of the device tree
267 Total tree size in bytes
272 """Return the start of the device tree struct area
280 """Pack the device tree to remove unused space
282 This adjusts the tree in place.
367 """Holds a device tree property name and value.
369 This holds a copy of a property taken from the device tree. It does not
[all …]
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/ |
| H A D | README | 4 This directory contains device tree bindings for U-Boot.
8 This makes it easier for device tree people to review these additions in
|
| /rk3399_rockchip-uboot/doc/device-tree-bindings/video/bridge/ |
| H A D | ps8622.txt | 6 - sleep-gpios: OF device-tree gpio specification for PD_ pin.
7 - reset-gpios: OF device-tree gpio specification for RST_ pin.
|
| /rk3399_rockchip-uboot/arch/arm/dts/ |
| H A D | exynos4412.dtsi | 2 * Samsung's Exynos4412 SoC device tree source
12 * Exynos4412 SoC. As device tree coverage for Exynos4412 increases, additional
|