Home
last modified time | relevance | path

Searched refs:Tree (Results 1 – 25 of 1620) sorted by relevance

12345678910>>...65

/openbmc/openbmc/poky/bitbake/lib/toaster/toastergui/static/js/
H A Djquery.treetable.js9 var $, Node, Tree, methods; variable
242 Tree = (function() { function
243 function Tree(table, settings) { class in Tree
253 Tree.prototype.collapseAll = function() { class
264 Tree.prototype.expandAll = function() {
275 Tree.prototype.findLastNode = function (node) {
283 Tree.prototype.loadRows = function(rows) {
311 Tree.prototype.move = function(node, destination) {
341 Tree.prototype.removeNode = function(node) {
353 Tree.prototype.render = function() {
[all …]
/openbmc/linux/arch/arm/mach-spear/
H A DKconfig30 bool "SPEAr1310 Machine support with Device Tree"
37 bool "SPEAr1340 Machine support with Device Tree"
57 bool "SPEAr300 Machine support with Device Tree"
63 bool "SPEAr310 Machine support with Device Tree"
69 bool "SPEAr320 Machine support with Device Tree"
/openbmc/openbmc/poky/meta/recipes-devtools/python/
H A Dpython3-dtc_1.7.2.bb1 SUMMARY = "Python Library for the Device Tree Compiler"
3 DESCRIPTION = "A python library for the Device Tree Compiler, a tool used to manipulate Device Tree…
/openbmc/linux/Documentation/arch/arm/
H A Dmicrochip.rst205 Device Tree for AT91 SoCs and boards
207 All AT91 SoCs are converted to Device Tree. Since Linux 3.19, these products
211 Device Tree files and Device Tree bindings that apply to AT91 SoCs and boards are
213 any time. So, be sure to use a Device Tree Binary and a Kernel Image generated from
221 - SoCs Device Tree Source Include files are named after the official name of
223 - Device Tree Source Include files (.dtsi) are used to collect common nodes that can be
228 - board Device Tree Source files (.dts) are prefixed by the string "at91-" so
/openbmc/linux/arch/arm/mach-orion5x/
H A DKconfig21 bool "Marvell Orion5x Flattened Device Tree"
32 bool "Marvell Orion-NAS Reference Design (Flattened Device Tree)"
37 Orion-NAS (88F5182) RD2, Flattened Device Tree.
79 bool "Buffalo Linkstation Mini (Flattened Device Tree)"
107 bool "LaCie d2 Network / Big Disk Network (Flattened Device Tree)"
122 bool "Maxtor Shared Storage II (Flattened Device Tree)"
/openbmc/linux/drivers/of/
H A DKconfig6 bool "Device Tree and Open Firmware support"
16 bool "Device Tree runtime unit tests"
41 bool "Build all Device Tree Blobs"
45 This option builds all possible Device Tree Blobs (DTBs) for the
92 bool "Device Tree overlays"
/openbmc/linux/Documentation/ABI/stable/
H A Dsysfs-devices7 Contact: Device Tree mailing list <devicetree@vger.kernel.org>
15 Contact: Device Tree mailing list <devicetree@vger.kernel.org>
22 Contact: Device Tree mailing list <devicetree@vger.kernel.org>
/openbmc/openbmc/meta-openembedded/meta-perl/recipes-perl/libhtml/
H A Dlibhtml-tree-perl_5.03.bb9 HOMEPAGE = "https://metacpan.org/release/CJM/HTML-Tree-5.03/source/README"
14 SRC_URI = "${CPAN_MIRROR}/authors/id/C/CJ/CJM/HTML-Tree-${PV}.tar.gz \
19 S = "${WORKDIR}/HTML-Tree-${PV}"
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Darmada-370db-audio.txt1 Device Tree bindings for the Armada 370 DB audio
4 These Device Tree bindings are used to describe the audio complex
/openbmc/linux/Documentation/core-api/
H A Dmaple_tree.rst5 Maple Tree
13 The Maple Tree is a B-Tree data type which is optimized for storing
22 The Maple Tree maintains a small memory footprint and was designed to use
25 scenarios. The most important usage of the Maple Tree is the tracking of the
28 The Maple Tree can store values between ``0`` and ``ULONG_MAX``. The Maple
29 Tree reserves values with the bottom two bits set to '10' which are below 4096
36 The Maple Tree can also be configured to support searching for a gap of a given
100 The Maple Tree uses RCU and an internal spinlock to synchronise access:
120 structures that you are storing in the Maple Tree, you can call mtree_lock()
/openbmc/linux/arch/arm/boot/dts/marvell/
H A Darmada-xp-db-xc3-24g4xg.dts3 * Device Tree file for DB-XC3-24G4XG board
9 * Note: this Device Tree assumes that the bootloader has remapped the
16 * solution) or the below Device Tree should be adjusted.
H A Darmada-xp-crs305-1g-4s.dtsi3 * Device Tree file for CRS305-1G-4S board
10 * Note: this Device Tree assumes that the bootloader has remapped the
17 * solution) or the below Device Tree should be adjusted.
H A Darmada-xp-crs328-4c-20s-4s.dtsi3 * Device Tree file for CRS328-4C-20S-4S+ board
10 * Note: this Device Tree assumes that the bootloader has remapped the
17 * solution) or the below Device Tree should be adjusted.
H A Darmada-xp-crs326-24g-2s.dtsi3 * Device Tree file for CRS326-24G-2S board
10 * Note: this Device Tree assumes that the bootloader has remapped the
17 * solution) or the below Device Tree should be adjusted.
H A Darmada-xp-db-dxbc2.dts3 * Device Tree file for DB-DXBC2 board
9 * Note: this Device Tree assumes that the bootloader has remapped the
16 * solution) or the below Device Tree should be adjusted.
/openbmc/linux/Documentation/devicetree/bindings/fpga/
H A Dfpga-region.txt1 FPGA Region Device Tree Binding
11 - Device Tree Examples
19 the Device Tree. FPGA Regions provide a way to program FPGAs under device tree
114 4. The Device Tree overlay is accepted into the live tree.
133 The intended use is that a Device Tree overlay (DTO) can be used to reprogram an
136 An FPGA Region that exists in the live Device Tree reflects the current state.
281 a FPGA Region. The target of the Device Tree Overlay is the FPGA Region. Some
306 Device Tree Examples
317 For the purposes of this section, I'm dividing the Device Tree into two parts,
322 The live Device Tree must contain an FPGA Region, an FPGA Manager, and any FPGA
[all …]
/openbmc/u-boot/doc/device-tree-bindings/net/
H A Dfixed-link.txt1 Fixed link Device Tree binding
5 normal MDIO-managed PHY device. For those situations, a Device Tree
/openbmc/u-boot/dts/
H A DKconfig2 # Device Tree Control
22 menu "Device Tree Control"
26 bool "Run-time configuration via Device Tree"
33 bool "Board-specific manipulation of Device Tree"
37 make the Device Tree writeable and provides a board-specific
39 enables the board initialization to modifiy the Device Tree. The
43 bool "Enable run-time configuration via Device Tree in SPL"
51 bool "Enable run-time configuration via Device Tree in TPL"
114 string "Default Device Tree for DT control"
117 This option specifies the default Device Tree used for DT control.
/openbmc/openbmc/poky/meta/recipes-kernel/dtc/
H A Ddtc_1.7.2.bb1 SUMMARY = "Device Tree Compiler"
3 DESCRIPTION = "The Device Tree Compiler is a toolchain for working with device tree source and bina…
/openbmc/u-boot/board/ti/am65x/
H A DREADME107 Tree: git://git.ti.com/processor-firmware/system-firmware-image-gen.git
111 Tree: https://github.com/ARM-software/arm-trusted-firmware.git
115 Tree: https://github.com/OP-TEE/optee_os.git
119 Tree: http://git.denx.de/u-boot.git
/openbmc/linux/drivers/clk/sunxi/
H A DKconfig15 Device Tree backward compatibility issues, in case one would
16 still use a Device Tree with one clock provider by
/openbmc/linux/arch/arm64/boot/dts/marvell/
H A Dac5-98dx35xx-rd.dts3 * Device Tree For RD-AC5X.
9 * Device Tree file for Marvell Alleycat 5X development board
/openbmc/linux/drivers/hid/i2c-hid/
H A DKconfig34 This driver supports Open Firmware (Device Tree)-based systems as
50 the i2c-hid protocol on Open Firmware (Device Tree)-based
66 the i2c-hid protocol on Open Firmware (Device Tree)-based
/openbmc/u-boot/doc/uImage.FIT/
H A Dhowto.txt213 Description: Flattened Device Tree blob
214 Type: Flat Device Tree
263 Description: Flattened Device Tree blob
264 Type: Flat Device Tree
297 ## Flattened Device Tree from FIT Image at 00900000
300 Description: Flattened Device Tree blob
301 Type: Flat Device Tree
312 Loading Device Tree to 007fc000, end 007fffff ... OK
/openbmc/linux/drivers/char/xillybus/
H A DKconfig31 tristate "Xillybus over Device Tree"
35 Open Firmware Flattened Device Tree. If the target is an embedded

12345678910>>...65