| /OK3568_Linux_fs/u-boot/dts/ |
| H A D | Kconfig | 2 # Device Tree Control
22 menu "Device Tree Control"
26 bool "Run-time configuration via Device Tree"
29 This feature provides for run-time configuration of U-Boot
30 via a flattened device tree.
33 bool "Board-specific manipulation of Device Tree"
36 U-Boot's device tree (e.g. to delete device from it). This option
37 make the Device Tree writeable and provides a board-specific
38 "board_fix_fdt" callback (called during pre-relocation time), which
39 enables the board initialization to modifiy the Device Tree. The
[all …]
|
| /OK3568_Linux_fs/u-boot/doc/driver-model/ |
| H A D | fdt-fixup.txt | 1 Pre-relocation device tree manipulation
12 ----------
17 "extensions" of each other, where one device only differs from another in the
23 addition of the daughter board to the device realizes the "extension" of
24 functionality to the device described previously.
27 variations of the device. This means that the software somehow needs to cope
32 device tree overlay mechanism: There exists one "base" device tree, which
34 device. At the start of the kernel, the presence and type of the daughter
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
[all …]
|
| H A D | livetree.txt | 1 Driver Model with Live Device Tree
6 ------------
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.
18 ----------
20 The flat device tree has several advantages:
22 - it is the format produced by the device tree compiler, so no translation
[all …]
|
| H A D | of-plat.txt | 1 Driver Model Compiled-in Device Tree / Platform Data
6 ------------
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.
16 However there are some very constrained environments where U-Boot needs to
19 case the overhead of device tree access may be too great.
23 bypasses the use of device tree completely, effectively creating a parallel
26 As an alternative, a new 'of-platdata' feature is provided. This converts the
27 device tree contents into C code which can be compiled into the SPL binary.
[all …]
|
| H A D | pci-info.txt | 5 ----------------------
9 Bus number 0 will need to be requested first, and the alias in the device
10 tree file will point to the correct device:
17 pci: pci-controller {
23 If there is no alias the devices will be numbered sequentially in the 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
38 specify the driver to use for the device. In this case they will be bound at
39 first. Each PCI device node must have a compatible string list as well as a
[all …]
|
| /OK3568_Linux_fs/kernel/scripts/dtc/libfdt/ |
| H A D | fdt_overlay.c | 1 // SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause)
3 * libfdt - Flat Device Tree manipulation
15 * overlay_get_target_phandle - retrieves the target phandle of a fragment
16 * @fdto: pointer to the device tree overlay blob
21 * property) instead of a path (target-path property).
26 * -1, if the phandle was malformed
37 if ((len != sizeof(*val)) || (fdt32_to_cpu(*val) == (uint32_t)-1)) in overlay_get_target_phandle()
38 return (uint32_t)-1; in overlay_get_target_phandle()
44 * overlay_get_target - retrieves the offset of a fragment's target
45 * @fdt: Base device tree blob
[all …]
|
| H A D | libfdt.h | 1 /* SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause) */
5 * libfdt - Flat Device Tree manipulation
26 /* FDT_ERR_NOSPACE: Operation needed to expand the device
27 * tree, but its buffer did not have sufficient space to
28 * contain the expanded tree. Use fdt_open_into() to move the
29 * device tree to a buffer with more space. */
34 * offset which is out-of-bounds, or which points to an
43 * length, or the phandle value was either 0 or -1, which are
46 /* FDT_ERR_BADSTATE: Function was passed an incomplete device
47 * tree created by the sequential-write functions, which is
[all …]
|
| H A D | libfdt_internal.h | 1 /* SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause) */
5 * libfdt - Flat Device Tree manipulation
10 #define FDT_ALIGN(x, a) (((x) + (a) - 1) & ~((a) - 1))
64 * You should have another method of validating the device tree, such as a
72 * This does essentially no checks. Only the latest device-tree
73 * version is correctly handled. Inconsistencies or errors in the device
74 * tree may cause undefined behaviour or crashes. Invalid parameters
77 * If an error occurs when modifying the tree it may leave the tree in
83 * Only use this if you have a fully validated device tree with
89 * This assumes that the device tree is sane. i.e. header metadata
[all …]
|
| /OK3568_Linux_fs/u-boot/scripts/dtc/libfdt/ |
| H A D | fdt_overlay.c | 9 * overlay_get_target_phandle - retrieves the target phandle of a fragment
10 * @fdto: pointer to the device tree overlay blob
15 * property) instead of a path (target-path property).
20 * -1, if the phandle was malformed
31 if ((len != sizeof(*val)) || (fdt32_to_cpu(*val) == (uint32_t)-1)) in overlay_get_target_phandle()
32 return (uint32_t)-1; in overlay_get_target_phandle()
38 * overlay_get_target - retrieves the offset of a fragment's target
39 * @fdt: Base device tree blob
40 * @fdto: Device tree overlay blob
45 * device tree of a fragment, no matter how the actual targetting is
[all …]
|
| H A D | libfdt.h | 4 * libfdt - Flat Device Tree manipulation
23 * MA 02110-1301 USA
67 /* FDT_ERR_NOSPACE: Operation needed to expand the device
68 * tree, but its buffer did not have sufficient space to
69 * contain the expanded tree. Use fdt_open_into() to move the
70 * device tree to a buffer with more space. */
75 * offset which is out-of-bounds, or which points to an
84 * length, or the phandle value was either 0 or -1, which are
87 /* FDT_ERR_BADSTATE: Function was passed an incomplete device
88 * tree created by the sequential-write functions, which is
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/ |
| H A D | of_unittest.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Open Firmware Device Tree Unittest
13 is attached to the live tree dynamically, independent of the machine's
18 (1) Documentation/devicetree/usage-model.rst
22 provided to device driver developers to fetch the device information..etc.
23 from the unflattened device tree data structure. This interface is used by
24 most of the device drivers in various use cases.
27 2. Test-data
30 The Device Tree Source file (drivers/of/unittest-data/testcases.dts) contains
32 drivers/of/unittest.c. Currently, following Device Tree Source Include files
[all …]
|
| H A D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Linux and the Device Tree
7 The Linux usage model for device tree data
11 This article describes how Linux uses the device tree. An overview of
12 the device tree data format can be found on the device tree usage page
17 The "Open Firmware Device Tree", or simply Device Tree (DT), is a data
23 Structurally, the DT is a tree, or acyclic graph with named nodes, and
26 links from one node to another outside of the natural tree structure.
29 is defined for how data should appear in the tree to describe typical
44 ----------
[all …]
|
| /OK3568_Linux_fs/buildroot/linux/ |
| H A D | Config.in | 9 your embedded device
14 # but do not use the kernel-modules infrastructure, should select that
38 bool "Latest CIP SLTS version (5.10.162-cip24)"
44 automation and more for reliable and secure Linux-based
48 of industrial-grade software that permits the use and
55 https://www.cip-project.org
58 bool "Latest CIP RT SLTS version (5.10.162-cip24-rt10)"
67 https://www.cip-project.org
89 the Buildroot tree.
97 the root of the Buildroot tree.
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-spear/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
30 bool "SPEAr1310 Machine support with Device Tree"
34 Supports ST SPEAr1310 machine configured via the device-tree
37 bool "SPEAr1340 Machine support with Device Tree"
41 Supports ST SPEAr1340 machine configured via the device-tree
57 bool "SPEAr300 Machine support with Device Tree"
60 Supports ST SPEAr300 machine configured via the device-tree
63 bool "SPEAr310 Machine support with Device Tree"
66 Supports ST SPEAr310 machine configured via the device-tree
69 bool "SPEAr320 Machine support with Device Tree"
[all …]
|
| /OK3568_Linux_fs/kernel/drivers/of/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
6 bool "Device Tree and Open Firmware support"
8 This option enables the device tree infrastructure.
11 compile-coverage.
19 Set DTC_FLAGS += -@
37 bool "Device Tree runtime unit tests"
43 This option builds in test cases for the device tree infrastructure
50 bool "Build all Device Tree Blobs"
54 This option builds all possible Device Tree Blobs (DTBs) for the
79 bool "Support for dynamic device trees" if OF_UNITTEST
[all …]
|
| H A D | fdt.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * Functions for working with the Flattened Device Tree data format
35 * of_fdt_limit_memory - limit the number of regions in the /memory node
38 * Adjust the flattened device tree to have at most 'limit' number of
59 "#address-cells", NULL); in of_fdt_limit_memory()
64 "#size-cells", NULL); in of_fdt_limit_memory()
118 pprev = &np->properties; in populate_properties()
145 /* We accept flattened tree phandles either in in populate_properties()
146 * ePAPR-style "phandle" properties, or the in populate_properties()
153 if (!np->phandle) in populate_properties()
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/powerpc/ |
| H A D | bootwrapper.rst | 17 others. U-Boot is typically found on embedded PowerPC hardware, but there
28 U-Boot (for versions that don't understand the device
29 tree). This image embeds a device tree blob inside
30 the image. The boot wrapper, kernel and device tree
31 are all embedded inside the U-Boot uImage file format
33 bd_info structure and loads the data into the device
34 tree before jumping into the kernel.
37 bd_info structure used in the old U-Boot interfaces,
39 U-Boot platform has a different platform init file
40 which populates the embedded device tree with data
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-firmware-ofw | 5 When using OpenFirmware or a Flattened Device Tree to enumerate
6 hardware, the device tree structure will be exposed in this
9 It is possible for multiple device-tree directories to exist.
10 Some device drivers use a separate detached device tree which
11 have no attachment to the system tree and will appear in a
15 path directly, but instead should follow /proc/device-tree
19 The /proc/device-tree symlink replaces the devicetree /proc
24 hierarchy of directories, one per device tree node. The
28 binary data from the device tree.
42 /sys/firmware/device-tree is deliberate: FDT is also used
|
| /OK3568_Linux_fs/u-boot/include/dm/ |
| H A D | root.h | 7 * SPDX-License-Identifier: GPL-2.0+
16 * dm_root() - Return pointer to the top of the driver tree
18 * This function returns pointer to the root node of the driver tree,
20 * @return pointer to root device, or NULL if not inited yet
26 * dm_fixup_for_gd_move() - Handle global_data moving to a new place
35 * dm_scan_platdata() - Scan all platform data and bind drivers
41 * @return 0 if OK, -ve on error
46 * dm_scan_fdt() - Scan the device tree and bind drivers
48 * This scans the device tree and creates a driver for each node. Only
49 * the top-level subnodes are examined.
[all …]
|
| H A D | device-internal.h | 8 * SPDX-License-Identifier: GPL-2.0+
20 * device_bind() - Create a device and bind it to a driver
22 * Called to set up a new device attached to a driver. The device will either
23 * have platdata, or a device tree node which can be used to create the
26 * Once bound a device exists but is not yet active until device_probe() is
29 * @parent: Pointer to device's parent, under which this driver will exist
30 * @drv: Device's driver
31 * @name: Name of device (e.g. device tree node name)
32 * @platdata: Pointer to data for this device - the structure is device-
33 * specific but may include the device's I/O address, etc.. This is NULL for
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/fpga/ |
| H A D | fpga-region.txt | 1 FPGA Region Device Tree Binding
6 - Introduction
7 - Terminology
8 - Sequence
9 - FPGA Region
10 - Supported Use Models
11 - Device Tree Examples
12 - Constraints
19 the Device Tree. FPGA Regions provide a way to program FPGAs under device tree
22 This device tree binding document hits some of the high points of FPGA usage and
[all …]
|
| /OK3568_Linux_fs/u-boot/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
22 peripheral device is associated with.
24 If this option is disabled (it is the only possible choice for non-DT
27 It is totally up to the implementation of each low-level driver.
40 If you need to handle vendor-specific DT properties, you can disable
53 The driver is typically controlled by the device tree.
66 This option is an SPL-variant of the PINCTRL option.
75 This option is an SPL-variant of the PINCTRL_FULL option.
[all …]
|
| /OK3568_Linux_fs/u-boot/tools/dtoc/ |
| H A D | fdt.py | 6 # SPDX-License-Identifier: GPL-2.0+
15 # This deals with a device tree, presenting it as an assortment of Node and
17 # contains the base classes and defines the high-level API. You can use
20 # This implementation uses a libfdt Python library to access the device tree,
32 """A device tree property
35 name: Property name (as per the device tree)
105 TYPE_INT: a byte-swapped integer stored as a 4-byte string
106 TYPE_BYTE: a byte stored as a single-byte string
112 count = len(strings) - 1
113 if count > 0 and not strings[-1]:
[all …]
|
| /OK3568_Linux_fs/kernel/arch/arm/mach-omap2/ |
| H A D | board-generic.c | 1 // SPDX-License-Identifier: GPL-2.0-only
6 * Copyright (C) 2011 Texas Instruments Incorporated - https://www.ti.com/
8 * Modified from the original mach-omap/omap2/board-generic.c did by Paul
9 * to support the OMAP2+ device tree boards with an unique board file.
24 { .compatible = "simple-bus", },
25 { .compatible = "ti,omap-infra", },
42 /* Used by am437x for ARM timer in non-SMP configurations */
55 DT_MACHINE_START(OMAP242X_DT, "Generic OMAP2420 (Flattened Device Tree)")
72 DT_MACHINE_START(OMAP243X_DT, "Generic OMAP2430 (Flattened Device Tree)")
86 "nokia,omap3-n900",
[all …]
|
| /OK3568_Linux_fs/buildroot/package/dtc/ |
| H A D | Config.in | 5 The Device Tree Compiler, dtc, takes as input a device-tree in
6 a given format and outputs a device-tree in another format.
20 - convert-dtsv0 convert from version 0 to version 1
21 - dtc the device tree compiler
22 - dtdiff compare two device trees (needs bash)
23 - fdtdump print a readable version of a
24 flat device tree
25 - fdtget read values from device tree
26 - fdtput write a property value to a device tree
|