Searched full:nodes (Results 1 – 25 of 934) sorted by relevance
12345678910>>...38
| /Documentation/devicetree/bindings/usb/ |
| D | usb-device.txt | 7 Four types of device-tree nodes are defined: "host-controller nodes"
8 representing USB host controllers, "device nodes" representing USB devices,
9 "interface nodes" representing USB interfaces and "combined nodes"
20 Required properties for device nodes:
30 Required properties for device nodes with interface nodes:
35 Required properties for interface nodes:
49 Required properties for combined nodes:
59 Required properties for hub nodes with device nodes:
64 Required properties for host-controller nodes with device nodes:
|
| /Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 19 which is an administrative mechanism for restricting the nodes from which
42 allocations across all nodes with "sufficient" memory, so as
166 an optional set of nodes. The mode determines the behavior of the
168 and the optional set of nodes can be viewed as the arguments to the
190 does not use the optional set of nodes.
192 It is an error for the set of nodes specified for this policy to
197 nodes specified by the policy. Memory will be allocated from
204 allocation fails, the kernel will search other nodes, in order
224 page granularity, across the nodes specified in the policy.
229 Interleave mode indexes the set of nodes specified by the
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | meson,pinctrl.txt | 20 === GPIO sub-nodes ===
25 Required properties for sub-nodes are:
34 === Other sub-nodes ===
36 Child nodes without the "gpio-controller" represent some desired
37 configuration for a pin or a group. Those nodes can be pinmux nodes or
38 configuration nodes.
40 Required properties for pinmux nodes are:
47 Required properties for configuration nodes:
50 Configuration nodes support the following generic properties, as
|
| D | xlnx,zynq-pinctrl.txt | 12 Zynq's pin configuration nodes act as a container for an arbitrary number of
18 Each configuration node can consist of multiple nodes describing the pinmux and
19 pinconf options. Those nodes can be pinmux nodes or pinconf nodes.
24 Required properties for pinmux nodes are:
29 Required properties for configuration nodes:
|
| /Documentation/vm/ |
| D | numa.rst | 49 abstractions called "nodes". Linux maps the nodes onto the physical cells
51 architectures. As with physical cells, software nodes may contain 0 or more
53 "closer" nodes--nodes that map to closer cells--will generally experience
64 the emulation of additional nodes. For NUMA emulation, linux will carve up
65 the existing nodes--or the system memory for non-NUMA platforms--into multiple
66 nodes. Each emulated node will manage a fraction of the underlying cells'
76 an ordered "zonelist". A zonelist specifies the zones/nodes to visit when a
81 Because some nodes contain multiple zones containing different types of
87 from the same node before using remote nodes which are ordered by NUMA distance.
94 nodes' zones in the selected zonelist looking for the first zone in the list
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-fsi.txt | 9 nodes.
10 - #size-cells = <0>; : Number of size cells in child nodes.
11 - child nodes : Nodes to describe busses off the I2C
18 - child nodes : Nodes to describe devices on the I2C
|
| D | i2c-mux.txt | 4 numbered uniquely in a device dependent manner. The nodes for an i2c bus
15 For i2c multiplexers/switches that have child nodes that are a mixture
16 of both i2c child busses and other child nodes, the 'i2c-mux' subnode
25 Required properties for i2c child bus nodes:
30 Optional properties for i2c child bus nodes:
32 - Child nodes conforming to i2c bus binding
|
| /Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 20 For instance in a system where CPUs support SMT, "cpu" nodes represent all
22 In systems where SMT is not supported "cpu" nodes represent all cores present
25 CPU topology bindings allow one to associate cpu nodes with hierarchical groups
27 tree nodes.
32 The cpu nodes, as per bindings defined in [4], represent the devices that
35 A topology description containing phandles to cpu nodes that are not compliant
44 nodes are listed.
60 The cpu-map node's child nodes can be:
62 - one or more cluster nodes or
63 - one or more socket nodes in a multi-socket system
[all …]
|
| /Documentation/sphinx/ |
| D | automarkup.py | 7 from docutils import nodes
46 repl.append(nodes.Text(t[done:m.start()]))
51 target_text = nodes.Text(target + '()')
54 lit_text = nodes.literal(classes=['xref', 'c', 'c-func'])
79 repl.append(nodes.Text(t[done:]))
86 # kinds of nodes to prune. But this works well for now.
88 # The nodes.literal test catches ``literal text``, its purpose is to
92 for para in doctree.traverse(nodes.paragraph):
93 for node in para.traverse(nodes.Text):
94 if not isinstance(node.parent, nodes.literal):
|
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 54 node may write to those sectors. This is used when a new nodes
60 Each node has to communicate with other nodes when starting or ending
70 Normally all nodes hold a concurrent-read lock on this device.
75 Messages can be broadcast to all nodes, and the sender waits for all
76 other nodes to acknowledge the message before proceeding. Only one
87 informs other nodes that the metadata has
94 informs other nodes that a resync is initiated or
104 informs other nodes that a device is being added to
128 The DLM LVB is used to communicate within nodes of the cluster. There
145 acknowledged by all nodes in the cluster. The BAST of the resource
[all …]
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 19 acpi_device objects are referred to as "device nodes" in what follows, but they
23 During ACPI-based device hot-remove device nodes representing pieces of hardware
27 initialization of device nodes, such as retrieving common configuration
48 where ids is the list of IDs of device nodes the given handler is supposed to
51 executed, respectively, after registration of new device nodes and before
52 unregistration of device nodes the handler attached to previously.
55 device nodes in the given namespace scope with the driver core. Then, it tries
72 callbacks from the scan handlers of all device nodes in the given namespace
74 nodes in that scope.
79 is the order in which they are matched against device nodes during namespace
|
| /Documentation/filesystems/ |
| D | ubifs-authentication.rst | 76 - *Index*: an on-flash B+ tree where the leaf nodes contain filesystem data
94 Basic on-flash UBIFS entities are called *nodes*. UBIFS knows different types
95 of nodes. Eg. data nodes (`struct ubifs_data_node`) which store chunks of file
96 contents or inode nodes (`struct ubifs_ino_node`) which represent VFS inodes.
97 Almost all types of nodes share a common header (`ubifs_ch`) containing basic
100 and some less important node types like padding nodes which are used to pad
104 as *wandering tree*, where only the changed nodes are re-written and previous
117 a dirty-flag which marks nodes that have to be persisted the next time the
122 on-flash filesystem structures like the index. On every commit, the TNC nodes
131 any changes (in form of inode nodes, data nodes etc.) between commits
[all …]
|
| /Documentation/devicetree/bindings/media/ |
| D | exynos4-fimc-is.txt | 30 The following are the FIMC-IS peripheral device nodes and can be specified
31 either standalone or as the fimc-is node child nodes.
33 i2c-isp (ISP I2C bus controller) nodes
44 For the above nodes it is required to specify a pinctrl state named "default",
47 Device tree nodes of the image sensors' controlled directly by the FIMC-IS
48 firmware must be child nodes of their corresponding ISP I2C bus controller node.
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-tipwmss.txt | 10 - address-cells: Specify the number of u32 entries needed in child nodes.
12 - size-cells: specify number of u32 entries needed to specify child nodes size
20 Also child nodes should also populated under PWMSS DT node.
33 /* child nodes go here */
46 /* child nodes go here */
57 /* child nodes go here */
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-node | 5 Nodes that could be possibly become online at some point.
11 Nodes that are online.
17 Nodes that have regular memory.
23 Nodes that have one or more CPUs.
29 Nodes that have regular or high memory.
70 Distance between the node and all the other nodes
99 The node's relationship to other nodes for access class "Y".
106 nodes that have class "Y" access to this target node's
107 memory. CPUs and other memory initiators in nodes not in
123 nodes found in this access class's linked initiators.
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell-pxa168.txt | 11 - #address-cells: must be 1 when using sub-nodes.
12 - #size-cells: must be 0 when using sub-nodes.
18 Sub-nodes:
21 Sub-nodes required properties:
|
| /Documentation/devicetree/bindings/ |
| D | graph.txt | 10 There already is a simple directed graph between devices tree nodes using
11 phandle properties pointing to other nodes to describe connections that
30 Ports are described by child 'port' nodes contained in the device node.
37 and 'reg' properties is used to number the nodes.
66 All 'port' nodes can be grouped under an optional 'ports' node, which
68 nodes independently from any other child device nodes a device might
117 property present in the port and/or endpoint nodes then the following
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap4-dss.txt | 17 Required nodes:
20 Optional nodes:
54 Optional nodes:
70 Optional nodes:
91 Optional nodes:
114 Optional nodes:
|
| D | ti,omap5-dss.txt | 17 Required nodes:
20 Optional nodes:
54 Optional nodes:
72 Optional nodes:
95 Optional nodes:
|
| /Documentation/devicetree/bindings/iio/ |
| D | iio-bindings.txt | 5 tree. Those nodes are designated as IIO providers. IIO consumer
6 nodes use a phandle and IIO specifier pair to connect IIO provider
17 #io-channel-cells: Number of cells in an IIO specifier; Typically 0 for nodes
18 with a single IIO output and 1 for nodes with multiple
60 Empty property indicating that child nodes can inherit named
61 IIO channels from this node. Useful for bus nodes to provide
|
| /Documentation/devicetree/bindings/clock/ |
| D | st,nomadik.txt | 23 PLL nodes: these nodes represent the two PLLs on the system,
27 Required properties for the two PLL nodes:
34 HCLK nodes: these represent the clock gates on individual
38 Requires properties for the HCLK nodes:
|
| /Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.yaml | 19 Since simplefb nodes represent runtime information they must be
20 sub-nodes of the chosen node (*). Simplefb nodes must be named
23 If the devicetree contains nodes for the display hardware used by a
28 hw nodes must specify which node is considered the primary node.
43 framebuffer nodes, so that the firmware only needs to update the
45 for more display clocks get added, the simplefb nodes will already
48 If pre-filled framebuffer nodes are used, the firmware may need
|
| /Documentation/media/dvb-drivers/ |
| D | udev.rst | 24 DVB device nodes are created automatically.
27 creating the DVB device nodes manually up to now due to the missing sysfs
31 device nodes manually.
47 1. You need to create a proper udev rule that will create the device nodes
58 If you want more control over the device nodes (for example a special group membership)
|
| /Documentation/devicetree/bindings/power/ |
| D | renesas,sysc-rmobile.txt | 22 Optional nodes:
23 - pm-domains: This node contains a hierarchy of PM domain nodes, which should
28 == PM Domain Nodes ==
30 Each of the PM domain nodes represents a PM domain, as documented by the
34 The nodes should be named by the real power area names, and thus their names
|
| /Documentation/media/kapi/ |
| D | v4l2-intro.rst | 7 hardware: most devices have multiple ICs, export multiple device nodes in
18 creating V4L device nodes and video_buf for handling the video buffers
46 3) Creating V4L2 device nodes (/dev/videoX, /dev/vbiX and /dev/radioX)
61 \-V4L2 device nodes
75 driver sets the struct v4l2_device mdev field, sub-devices and video nodes
|
12345678910>>...38