| /linux/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 manipulatio
[all...] |
| H A D | libfdt.h | 1 /* SPDX-License-Identifier: (GPL-2.0-or-later OR BSD-2-Clause) */
5 * libfdt - Flat Device Tree manipulatio
[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 manipulatio
[all...] |
| /linux/drivers/of/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
12 bool "Device Tree and Open Firmware support"
14 This option enables the device tree infrastructure.
17 compile-coverage.
22 bool "Device Tree runtime unit tests"
27 This option builds in test cases for the device tree infrastructure
50 This option builds KUnit unit tests for device tree infrastructure.
55 bool "Build all Device Tree Blobs"
59 This option builds all possible Device Tree Blobs (DTBs) for the
84 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
43 * of_fdt_limit_memory - limit the number of regions in the /memory node
46 * Adjust the flattened device tree to have at most 'limit' number of
105 pprev = &np->properties; in populate_properties()
132 /* We accept flattened tree phandles either in in populate_properties()
133 * ePAPR-style "phandle" properties, or the in populate_properties()
140 if (!np->phandle) in populate_properties()
141 np->phandle = be32_to_cpup(val); in populate_properties()
145 * used in pSeries dynamic device tree in populate_properties()
[all …]
|
| /linux/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 …]
|
| /linux/Documentation/arch/arm/google/ |
| H A 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 …]
|
| /linux/Documentation/arch/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 …]
|
| /linux/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
|
| /linux/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 …]
|
| /linux/arch/arm/mach-mvebu/ |
| H A 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.
|
| /linux/Documentation/arch/arm/ |
| H A D | microchip.rst | 7 ------------
11 It is important to note that the Microchip (previously Atmel) ARM-based MPU
15 git branches/tags and email subject always contain this "at91" sub-string.
19 ---------
25 - at91rm9200
29 …http://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-1768-32-bit-ARM920T-Embedded-Microprocessor-…
32 - at91sam9260
36 …ttp://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-6221-32-bit-ARM926EJ-S-Embedded-Microprocesso…
38 - at91sam9xe
42 …ttp://ww1.microchip.com/downloads/en/DeviceDoc/Atmel-6254-32-bit-ARM926EJ-S-Embedded-Microprocesso…
[all …]
|
| /linux/arch/arm/mach-orion5x/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
15 Orion-1 (5181), Orion-VoIP (5181L), Orion-NAS (5182),
16 Orion-2 (5281), Orion-1-90 (6183).
21 bool "Marvell Orion5x Flattened Device Tree"
29 Marvell Orion5x using flattened device tree.
32 bool "Marvell Orion-NAS Reference Design (Flattened Device Tree)"
37 Orion-NAS (88F5182) RD2, Flattened Device Tree.
48 bool "D-Link DNS-323"
53 D-Link DNS-323 platform.
56 bool "QNAP TS-109/TS-209"
[all …]
|
| /linux/sound/hda/core/ |
| H A D | sysfs.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * sysfs support for HD-audio core device
8 #include <linux/device.h>
20 static ssize_t type##_show(struct device *dev, \
25 return sysfs_emit(buf, "0x%x\n", codec->type); \
30 static ssize_t type##_show(struct device *dev, \
36 codec->type ? codec->type : ""); \
49 static ssize_t modalias_show(struct device *dev, struct device_attribute *attr, in modalias_show()
79 * Widget tree sysfs
81 * This is a tree showing the attributes of each widget. It appears like
[all …]
|
| /linux/arch/powerpc/include/uapi/asm/ |
| H A D | bootx.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
54 the map is optional and current BootX will only build it for pre-PCI
64 * Note that the kernel arguments and the device tree are appended
83 /* The device tree (internal addresses relative to the beginning of the tree,
84 * device tree offset relative to the beginning of this structure).
85 * On pre-PCI macintosh (BOOT_ARCH_PCI bit set to 0 in architecture), this
88 __u32 deviceTreeOffset; /* Device tree offset */
89 __u32 deviceTreeSize; /* Size of the device tree */
111 (non-PCI) only. On PCI, memory is contiguous and its size is in the
112 device-tree. */
[all …]
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-devices | 2 This documents additional properties of any device beyond what
3 is documented in Documentation/admin-guide/sysfs-rules.rst
7 Contact: Device Tree mailing list <devicetree@vger.kernel.org>
9 Any device associated with a device-tree node will have
10 an of_path symlink pointing to the corresponding device
15 Contact: Device Tree mailing list <devicetree@vger.kernel.org>
18 read, it returns full name of the device node.
22 Contact: Device Tree mailing list <devicetree@vger.kernel.org>
25 read, it returns full name of the device node.
29 Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
[all …]
|
| /linux/Documentation/devicetree/bindings/iio/ |
| H A D | common.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jonathan Cameron <jic23@kernel.org>
11 - Guido Günther <agx@sigxcpu.org>
14 This document defines device tree properties common to several iio
15 sensors. It doesn't constitute a device tree binding specification by itself but
16 is meant to be referenced by device tree bindings.
18 When referenced from sensor tree bindings the properties defined in this
19 document are defined as follows. The sensor tree bindings are responsible for
[all …]
|
| /linux/arch/arm/mach-pxa/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
3 bool "PXA2xx/PXA3xx-based"
20 bool "Support PXA25x platforms from device tree"
27 the device tree. Needn't select any other machine while
31 bool "Support PXA27x platforms from device tree"
38 the device tree. Needn't select any other machine while
42 bool "Support PXA3xx platforms from device tree"
52 the device tree. Needn't select any other machine while
64 Basix, Connex, ws-200ax, ws-400ax systems
79 bool "SHARP Zaurus SL-5600, SL-C7xx and SL-Cxx00 Models"
[all …]
|
| /linux/Documentation/devicetree/bindings/display/bridge/ |
| H A D | snps,dw-mipi-dsi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/snps,dw-mipi-dsi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Philippe CORNU <philippe.cornu@foss.st.com>
13 This document defines device tree properties for the Synopsys DesignWare MIPI
14 DSI host controller. It doesn't constitute a device tree binding specification
15 by itself but is meant to be referenced by platform-specific device tree
18 When referenced from platform device tree bindings the properties defined in
19 this document are defined as follows. The platform device tree bindings are
[all …]
|
| H A D | synopsys,dw-hdmi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/display/bridge/synopsys,dw-hdmi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
13 This document defines device tree properties for the Synopsys DesignWare HDMI
14 TX controller (DWC HDMI TX) IP core. It doesn't constitute a full device tree
15 binding specification by itself but is meant to be referenced by device tree
16 bindings for the platform-specific integrations of the DWC HDMI TX.
18 When referenced from platform device tree bindings the properties defined in
[all …]
|
| /linux/Documentation/devicetree/bindings/fpga/ |
| H A D | fpga-region.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/fpga/fpga-region.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Michal Simek <michal.simek@amd.com>
14 - Introduction
15 - Terminology
16 - Sequence
17 - FPGA Region
18 - Supported Use Models
[all …]
|
| /linux/include/uapi/linux/ |
| H A D | btrfs_tree.h | 1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
37 /* holds pointers to all of the tree roots */
44 * chunk tree stores translations from logical -> physical block numbering
45 * the super block points to the chunk tree
50 * stores information about which areas of a given device are in use.
51 * one per device. The tree of tree roots points to the device tree
58 /* directory objectid inside the root tree */
73 /* Holds the block group items for extent tree v2. */
79 /* device stats in the device tree */
82 /* for storing balance parameters in the root tree */
[all …]
|
| /linux/arch/powerpc/kernel/ |
| H A D | pci_of_scan.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Helper routines to scan the device tree for PCI devices and busses
17 #include <asm/pci-bridge.h>
20 * get_int_prop - Decode a u32 from a device tree property
34 * pci_parse_of_flags - Parse the flags cell of a device tree PCI address
35 * @addr0: value of 1st cell of a device tree PCI address.
38 * PCI Bus Binding to IEEE Std 1275-1994
49 * t is 1 if the address is aliased (for non-relocatable I/O),
54 * 10 denotes 32-bit-address Memory Space
55 * 11 denotes 64-bit-address Memory Space
[all …]
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | verity.rst | 2 dm-verity
5 Device-Mapper's "verity" target provides transparent integrity checking of
7 This target is read-only.
21 This is the type of the on-disk hash format.
32 This is the device containing data, the integrity of which needs to be
33 checked. It may be specified as a path, like /dev/sdaX, or a device number,
37 This is the device that supplies the hash tree data. It may be
38 specified similarly to the device path and may be the same device. If the
39 same device is used, the hash_start should be outside the configured
40 dm-verity device.
[all …]
|
| /linux/Documentation/arch/sh/ |
| H A D | booting.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------
6 Device-tree compatible SH bootloaders are expected to provide the physical
7 address of the device tree blob in r4. Since legacy bootloaders did not
9 inter-operate with old bootloaders must either use a builtin DTB or
11 that does not use device tree. Support for the latter is being phased out
12 in favor of device tree.
|