| /linux/drivers/android/binder/range_alloc/ |
| H A D | mod.rs | 118 Tree(TreeRangeAllocator<T>), enumerator
132 Impl::Tree(tree) => tree.free_oneway_space(), in free_oneway_space()
140 Impl::Tree(tree) => tree.count_buffers(), in count_buffers()
148 Impl::Tree(tree) => tree.debug_print(m), in debug_print()
187 self.inner = Impl::Tree(new_tree); in reserve_new()
201 Impl::Tree(tree) => { in reserve_new()
231 Impl::Tree(tree) => { in reservation_abort()
249 Impl::Tree(tree) => tree.reservation_commit(offset, data), in reservation_commit()
260 Impl::Tree(tree) => tree.reserve_existing(offset), in reserve_existing()
271 Impl::Tree(tree) => tree.take_for_each(callback), in take_for_each()
|
| /linux/arch/arm/mach-spear/ |
| H A D | Kconfig | 30 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"
|
| /linux/tools/perf/python/ |
| H A D | ilist.py | 18 from textual.widgets import Button, Footer, Header, Input, Label, Sparkline, Static, Tree
258 tree: Tree[TreeValue] = self.query_one("#root", Tree)
293 tree: Tree[str] = self.query_one("#root", Tree)
335 tree: Tree[str] = self.query_one("#root", Tree)
440 def metric_event_tree() -> Tree:
442 tree: Tree[TreeValue] = Tree("Root", id="root")
503 @on(Tree.NodeSelected)
504 def on_tree_node_selected(self, event: Tree.NodeSelected[TreeValue]) -> None:
|
| /linux/Documentation/arch/arm/ |
| H A D | microchip.rst | 205 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
|
| /linux/arch/arm/mach-orion5x/ |
| H A D | Kconfig | 21 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)"
|
| /linux/drivers/of/ |
| H A D | Kconfig | 12 bool "Device Tree and Open Firmware support"
22 bool "Device Tree runtime unit tests"
55 bool "Build all Device Tree Blobs"
59 This option builds all possible Device Tree Blobs (DTBs) for the
106 bool "Device Tree overlays"
117 tristate "Device Tree overlay KUnit tests" if !KUNIT_ALL_TESTS
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-devices | 7 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>
|
| /linux/Documentation/core-api/ |
| H A D | maple_tree.rst | 5 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
103 The Maple Tree uses RCU and an internal spinlock to synchronise access:
124 structures that you are storing in the Maple Tree, you can call mtree_lock()
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | armada-xp-crs328-4c-20s-4s.dtsi | 3 * 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 D | armada-xp-crs305-1g-4s.dtsi | 3 * 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 D | armada-xp-db-xc3-24g4xg.dts | 3 * 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 D | armada-xp-crs326-24g-2s.dtsi | 3 * 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 D | armada-xp-db-dxbc2.dts | 3 * 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 D | armada-xp-db.dts | 3 * Device Tree file for Marvell Armada XP evaluation board
13 * Note: this Device Tree assumes that the bootloader has remapped the
20 * solution) or the below Device Tree should be adjusted.
|
| H A D | armada-370-rd.dts | 3 * Device Tree file for Marvell Armada 370 Reference Design 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 D | armada-370-synology-ds213j.dts | 3 * Device Tree file for Synology DS213j
7 * Note: this Device Tree assumes that the bootloader has remapped the
14 * not be able to directly boot a kernel based on this Device Tree. In
17 * installing it from u-boot prompt) or adjust the Devive Tree
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | armada-370db-audio.txt | 1 Device Tree bindings for the Armada 370 DB audio
4 These Device Tree bindings are used to describe the audio complex
|
| /linux/drivers/hid/i2c-hid/ |
| H A D | Kconfig | 34 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
|
| /linux/arch/arm64/boot/dts/marvell/ |
| H A D | ac5-98dx35xx-rd.dts | 3 * Device Tree For RD-AC5X.
9 * Device Tree file for Marvell Alleycat 5X development board
|
| /linux/drivers/clk/sunxi/ |
| H A D | Kconfig | 15 Device Tree backward compatibility issues, in case one would
16 still use a Device Tree with one clock provider by
|
| /linux/arch/powerpc/boot/dts/fsl/ |
| H A D | gef_sbc610.dts | 3 * GE SBC610 Device Tree Source
7 * Based on: SBS CM6 Device Tree Source
9 * And: mpc8641_hpcn.dts (MPC8641 HPCN Device Tree Source)
|
| H A D | gef_ppc9a.dts | 3 * GE PPC9A Device Tree Source
7 * Based on: SBS CM6 Device Tree Source
9 * And: mpc8641_hpcn.dts (MPC8641 HPCN Device Tree Source)
|
| H A D | gef_sbc310.dts | 3 * GE SBC310 Device Tree Source
7 * Based on: SBS CM6 Device Tree Source
9 * And: mpc8641_hpcn.dts (MPC8641 HPCN Device Tree Source)
|
| /linux/drivers/char/xillybus/ |
| H A D | Kconfig | 31 tristate "Xillybus over Device Tree"
35 Open Firmware Flattened Device Tree. If the target is an embedded
|
| /linux/Documentation/devicetree/bindings/input/ |
| H A D | st-keyscan.txt | 1 * ST Keyscan controller Device Tree bindings
3 The ST keyscan controller Device Tree binding is based on the
|