Searched +full:device +full:- +full:tree (Results 1 – 25 of 1114) sorted by relevance
12345678910>>...45
| /kernel/linux/linux-5.10/Documentation/devicetree/ |
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-5.10/scripts/dtc/libfdt/ |
| 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 …]
|
| 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 …]
|
| 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 …]
|
| /kernel/linux/linux-6.6/scripts/dtc/libfdt/ |
| 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()
52 if (phandle == (uint32_t)-1) in fdt_overlay_target_offset()
53 return -FDT_ERR_BADPHANDLE; in fdt_overlay_target_offset()
[all …]
|
| D | libfdt.h | 1 /* SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause) */
5 * libfdt - Flat Device Tree manipulation
27 /* FDT_ERR_NOSPACE: Operation needed to expand the device
28 * tree, but its buffer did not have sufficient space to
29 * contain the expanded tree. Use fdt_open_into() to move the
30 * device tree to a buffer with more space. */
35 * offset which is out-of-bounds, or which points to an
44 * length, or the phandle value was either 0 or -1, which are
47 /* FDT_ERR_BADSTATE: Function was passed an incomplete device
48 * tree created by the sequential-write functions, which is
[all …]
|
| 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))
50 * Internal helpers to access tructural elements of the device tree
83 * You should have another method of validating the device tree, such as a
91 * This does essentially no checks. Only the latest device-tree
92 * version is correctly handled. Inconsistencies or errors in the device
93 * tree may cause undefined behaviour or crashes. Invalid parameters
96 * If an error occurs when modifying the tree it may leave the tree in
102 * Only use this if you have a fully validated device tree with
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-spear/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/ |
| D | of_unittest.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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.
45 from 'scripts/dtc/of_unittest_expect --help'.
48 3. Test-data
51 The Device Tree Source file (drivers/of/unittest-data/testcases.dts) contains
53 drivers/of/unittest.c. Currently, following Device Tree Source Include files
[all …]
|
| D | usage-model.rst | 1 .. SPDX-License-Identifier: GPL-2.0
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 Devicetree (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 ----------
48 Device Tree to discover the topology of the hardware at runtime, and
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/mach-spear/ |
| 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 …]
|
| /kernel/linux/linux-5.10/drivers/of/ |
| 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.
16 bool "Device Tree runtime unit tests"
22 This option builds in test cases for the device tree infrastructure
29 bool "Build all Device Tree Blobs"
33 This option builds all possible Device Tree Blobs (DTBs) for the
58 bool "Support for dynamic device trees" if OF_UNITTEST
61 On some platforms, the device tree can be manipulated at runtime.
[all …]
|
| /kernel/linux/linux-6.6/drivers/of/ |
| 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.
16 bool "Device Tree runtime unit tests"
22 This option builds in test cases for the device tree infrastructure
41 bool "Build all Device Tree Blobs"
45 This option builds all possible Device Tree Blobs (DTBs) for the
70 bool "Support for dynamic device trees" if OF_UNITTEST
73 On some platforms, the device tree can be manipulated at runtime.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/arch/arm/google/ |
| D | chromebook-boot-flow.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Most recent Chromebooks that use device tree are using the opensource
9 Image`_ which contains an OS image as well as a collection of device trees. It
10 is up to depthcharge_ to pick the right device tree from the `FIT Image`_ and
13 The scheme that depthcharge_ uses to pick the device tree takes into account
16 - Board name, specified at depthcharge_ compile time. This is $(BOARD) below.
17 - Board revision number, determined at runtime (perhaps by reading GPIO
19 - SKU number, read from GPIO strappings at boot time. This is $(SKU) below.
23 - google,$(BOARD)-rev$(REV)-sku$(SKU)
24 - google,$(BOARD)-rev$(REV)
[all …]
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| 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
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| 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
|
| /kernel/linux/linux-6.6/Documentation/powerpc/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| 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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/fpga/ |
| 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 …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/fpga/ |
| 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 …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| 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.
25 { .compatible = "simple-bus", },
26 { .compatible = "ti,omap-infra", },
43 /* Used by am437x for ARM timer in non-SMP configurations */
56 DT_MACHINE_START(OMAP242X_DT, "Generic OMAP2420 (Flattened Device Tree)")
73 DT_MACHINE_START(OMAP243X_DT, "Generic OMAP2430 (Flattened Device Tree)")
87 "nokia,omap3-n900",
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/mach-omap2/ |
| 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 …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-mvebu/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
38 on the Marvell Armada 370 SoC with device tree.
54 on the Marvell Armada 375 SoC with device tree.
72 on the Marvell Armada 380/385 SoC with device tree.
87 on the Marvell Armada 39x SoC with device tree.
99 on the Marvell Armada XP SoC with device tree.
114 Marvell Dove using flattened device tree.
130 on the Marvell Kirkwood device tree.
|
| /kernel/linux/linux-6.6/arch/arm/mach-mvebu/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
37 on the Marvell Armada 370 SoC with device tree.
53 on the Marvell Armada 375 SoC with device tree.
71 on the Marvell Armada 380/385 SoC with device tree.
86 on the Marvell Armada 39x SoC with device tree.
98 on the Marvell Armada XP SoC with device tree.
113 Marvell Dove using flattened device tree.
129 on the Marvell Kirkwood device tree.
|
12345678910>>...45