Home
last modified time | relevance | path

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

12345678910>>...60

/OK3568_Linux_fs/yocto/poky/bitbake/lib/toaster/toastergui/static/js/
H A Djquery.treetable.js9 var $, Node, Tree, methods;
242 Tree = (function() { class
243 function Tree(table, settings) { class in anonymousFunction75f42a160100.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 …]
/OK3568_Linux_fs/kernel/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"
/OK3568_Linux_fs/kernel/Documentation/arm/
H A Dmicrochip.rst185 Device Tree for AT91 SoCs and boards
187 All AT91 SoCs are converted to Device Tree. Since Linux 3.19, these products
191 Device Tree files and Device Tree bindings that apply to AT91 SoCs and boards are
193 any time. So, be sure to use a Device Tree Binary and a Kernel Image generated from
201 - SoCs Device Tree Source Include files are named after the official name of
203 - Device Tree Source Include files (.dtsi) are used to collect common nodes that can be
208 - board Device Tree Source files (.dts) are prefixed by the string "at91-" so
/OK3568_Linux_fs/kernel/drivers/of/
H A DKconfig6 bool "Device Tree and Open Firmware support"
37 bool "Device Tree runtime unit tests"
50 bool "Build all Device Tree Blobs"
54 This option builds all possible Device Tree Blobs (DTBs) for the
107 bool "Device Tree overlays"
/OK3568_Linux_fs/kernel/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>
/OK3568_Linux_fs/kernel/arch/arm/mach-orion5x/
H A DKconfig19 bool "Marvell Orion5x Flattened Device Tree"
44 bool "Marvell Orion-NAS Reference Design (Flattened Device Tree)"
49 Orion-NAS (88F5182) RD2, Flattened Device Tree.
86 bool "Buffalo Linkstation Mini (Flattened Device Tree)"
124 bool "LaCie d2 Network / Big Disk Network (Flattened Device Tree)"
138 bool "Maxtor Shared Storage II (Flattened Device Tree)"
/OK3568_Linux_fs/yocto/meta-openembedded/meta-perl/recipes-perl/libhtml/
H A Dlibhtml-tree-perl_5.03.bb9 HOMEPAGE = "http://www.cpan.org/authors/id/C/CJ/CJM/HTML-Tree-${PV}.readme"
14 SRC_URI = "${CPAN_MIRROR}/authors/id/C/CJ/CJM/HTML-Tree-${PV}.tar.gz \
20 S = "${WORKDIR}/HTML-Tree-${PV}"
/OK3568_Linux_fs/buildroot/boot/boot-wrapper-aarch64/
H A DConfig.in19 string "Device Tree Source name"
22 Name of the Device Tree Source file to use to generate the
23 Device Tree Blob that will be embedded in the image
/OK3568_Linux_fs/buildroot/package/dtbocfg/
H A DConfig.in5 dtbocfg, which stands for Device Tree Blob Overlay
7 as a userspace API of Device Tree Overlay.
/OK3568_Linux_fs/kernel/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.
286 a FPGA Region. The target of the Device Tree Overlay is the FPGA Region. Some
311 Device Tree Examples
322 For the purposes of this section, I'm dividing the Device Tree into two parts,
327 The live Device Tree must contain an FPGA Region, an FPGA Manager, and any FPGA
[all …]
/OK3568_Linux_fs/kernel/arch/arm/boot/dts/
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.
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.
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/memory-controllers/
H A Dmvebu-sdram-controller.txt1 Device Tree bindings for MVEBU SDRAM controllers
7 For now, this Device Tree binding documentation only documents the
/OK3568_Linux_fs/kernel/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
/OK3568_Linux_fs/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"
61 bool "Enable run-time configuration via Device Tree in TPL"
124 string "Default Device Tree for DT control"
127 This option specifies the default Device Tree used for DT control.
/OK3568_Linux_fs/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
/OK3568_Linux_fs/kernel/drivers/char/xillybus/
H A DKconfig27 tristate "Xillybus over Device Tree"
31 Open Firmware Flattened Device Tree. If the target is an embedded
/OK3568_Linux_fs/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
/OK3568_Linux_fs/yocto/poky/meta/recipes-kernel/dtc/
H A Ddtc_1.6.1.bb1 SUMMARY = "Device Tree Compiler"
3 DESCRIPTION = "The Device Tree Compiler is a tool used to manipulate the Open-Firmware-like device …
/OK3568_Linux_fs/u-boot/board/logicpd/omap3som/
H A DREADME6 By default, the Torpedo Device Tree is integrated into U-Boot,but the MMC controller, GPIO and I2C …
10 Integrating the SOM-LV Device Tree into U-Boot
/OK3568_Linux_fs/buildroot/linux/
H A DConfig.in390 bool "Build a Device Tree Blob (DTB)"
425 string "In-tree Device Tree Source file names"
432 string "Out-of-tree Device Tree Source file paths"
434 Paths to out-of-tree Device Tree Source (.dts) and Device Tree
440 bool "Keep the directory name of the Device Tree"
447 bool "Build Device Tree with overlay support"
450 symbols are generated in the compiled Device Tree.
451 Choose this option to support Device Tree overlays
464 Note that this option also installs the Device Tree Blobs to
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/video/
H A Drockchip_fb.txt1 Device-Tree bindings for Rockchip framebuffer.
16 Device-Tree bindings for RockChip screen driver
/OK3568_Linux_fs/u-boot/board/coreboot/coreboot/
H A DKconfig36 string "Board Device Tree Source (dts) file"
39 This option selects the board Device Tree Source (dts) file in
/OK3568_Linux_fs/kernel/Documentation/devicetree/
H A Ddynamic-resolution-notes.rst4 Device Tree Dynamic Resolver Notes
8 Device Tree resolver, residing in drivers/of/resolver.c
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/arm/marvell/
H A Darmada-37xx.txt1 Marvell Armada 37xx Platforms Device Tree Bindings
53 CZ.NIC's Turris Mox SOHO router Device Tree Bindings

12345678910>>...60