Searched full:child (Results 1 – 25 of 541) sorted by relevance
12345678910>>...22
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux.txt | 3 An i2c bus multiplexer/switch will have several child busses that are
5 multiplexer/switch will have one child node for each child bus.
9 This property is required if the i2c-mux child node does not exist.
12 This property is required if the i2c-mux child node does not exist.
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
17 can be used for populating the i2c child busses. If an 'i2c-mux'
19 child busses.
21 Required properties for the i2c-mux child node:
25 Required properties for i2c child bus nodes:
[all …]
|
| D | i2c-fsi.txt | 8 - #address-cells = <1>; : Number of address cells in child
10 - #size-cells = <0>; : Number of size cells in child nodes.
11 - child nodes : Nodes to describe busses off the I2C
14 Child node required properties:
17 Child node optional properties:
18 - child nodes : Nodes to describe devices on the I2C
|
| D | i2c-mux-pinctrl.txt | 12 | +---+ +------+ | child bus A, on first set of pins
14 | +---+ +------+ | child bus B, on second set of pins
28 * Standard pinctrl properties that specify the pin mux state for each child
33 * I2C child bus nodes. See i2c-mux.txt in this directory.
35 For each named state defined in the pinctrl-names property, an I2C child bus
36 will be created. I2C child bus numbers are assigned based on the index into
47 Whenever an access is made to a device on a child bus, the relevant pinctrl
51 on a child bus, the idle pinctrl state will be programmed into hardware.
55 a child bus.
|
| D | i2c-arb.txt | 3 - i2c-arb child node
5 Required properties for the i2c-arb child node:
9 Optional properties for i2c-arb child node:
10 - Child nodes conforming to i2c bus binding
|
| D | i2c-mux-gpio.txt | 11 | +------+ | +------+ child bus A, on GPIO value set to 0
13 | +------+ | +--+---+ child bus B, on GPIO value set to 1
26 * I2C child bus nodes. See i2c-mux.txt in this directory.
32 For each i2c child node, an I2C child bus will be created. They will
35 Whenever an access is made to a device on a child bus, the value set
40 whenever an access is not being made to a device on a child bus, the
45 device on a child bus.
|
| D | i2c-gate.txt | 9 - i2c-gate child node
11 Required properties for the i2c-gate child node:
15 Optional properties for i2c-gate child node:
16 - Child nodes conforming to i2c bus binding
|
| D | i2c-mux-gpmux.txt | 11 | .------. | .------+ child bus A, on MUX value set to 0
13 | '------' | '--+---+ child bus B, on MUX value set to 1
27 * I2C child bus nodes. See i2c-mux.txt in this directory. The sub-bus number
34 + between setup of the multiplexer and the child bus I2C transaction
35 + between the child bus I2C transaction and releasing of the multiplexer
47 For each i2c child node, an I2C child bus will be created. They will
50 Whenever an access is made to a device on a child bus, the value set
|
| /Documentation/networking/ |
| D | fib_trie.rst | 15 An internal node, holding an array of child (leaf or tnode) pointers,
22 child array - the "child index". See Level Compression.
26 the child array. See Path Compression.
29 Any given tnode is linked to from the child array of its parent, using
39 Level Compression / child arrays
41 children of a full child (see "full_children") up one level, so that
44 Conversely, a tnode with a mostly empty child array (see empty_children)
46 in order to avoid ever-increasing child arrays.
49 the number of positions in the child array of a given tnode that are
85 Analyzes a tnode and optimizes the child array size by either inflating
[all …]
|
| /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
15 physical address map of child's base address, physical address within
17 3 set of child register maps present, ECAP register space, EQEP
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/devicetree/bindings/slimbus/ |
| D | bus.txt | 9 Child nodes:
10 Every SLIMbus controller node can contain zero or more child nodes
15 If child node is not present and it is instantiated after device
20 such cases, child nodes for those devices will be present as
23 Required property for SLIMbus child node if it is present:
35 Optional property for SLIMbus child node if it is present:
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | ina3221.txt | 19 = The node contains optional child nodes for three channels =
20 = Each child node describes the information of input source =
22 - #address-cells: Required only if a child node is present. Must be 1.
23 - #size-cells: Required only if a child node is present. Must be 0.
25 2) child nodes
|
| /Documentation/devicetree/bindings/mtd/ |
| D | samsung-s3c2410.txt | 13 Optional child nodes:
14 Child nodes representing the available nand chips.
16 Optional child properties:
20 Each child device node may optionally contain a 'partitions' sub-node,
|
| D | aspeed-smc.txt | 20 - #address-cells : must be 1 corresponding to chip select child binding
21 - #size-cells : must be 0 corresponding to chip select child binding
27 The child nodes are the SPI flash modules which must have a compatible
30 Optionally, the child node can contain properties for SPI mode (may be
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,gsbi.txt | 3 The GSBI controller is modeled as a node with zero or more child nodes, each
20 - syscon-tcsr: indicates phandle of TCSR syscon node. Required if child uses
23 Required properties if child node exists:
30 A GSBI controller node can contain 0 or more child nodes representing serial
34 See the following for child node definitions:
57 /* child nodes go under here */
|
| /Documentation/admin-guide/cgroup-v1/ |
| D | pids.rst | 34 pids.current tracks all child cgroup hierarchies, so parent/pids.current is a
35 superset of parent/child/pids.current.
51 # mkdir -p /sys/fs/cgroup/pids/parent/child
67 Even if we migrate to a child cgroup (which doesn't have a set limit), we will
71 # echo $$ > /sys/fs/cgroup/pids/parent/child/cgroup.procs
74 # cat /sys/fs/cgroup/pids/parent/child/pids.current
76 # cat /sys/fs/cgroup/pids/parent/child/pids.max
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | samsung-pinctrl.txt | 47 - Pin banks as child nodes: Pin banks of the controller are represented by child
66 - Pin mux/config groups as child nodes: The pin mux (selecting pin function
68 as child nodes of the pin-controller node. There should be at least one
69 child node and there is no limit on the count of these child nodes. It is
70 also possible for a child node to consist of several further child nodes
72 level child nodes is exactly the same as for first level ones and is
75 The child node should contain a list of pin(s) on which a particular pin
87 child node is specified using the "samsung,pin-function" property. The value
90 for the specified pin group. This property is optional in the child node if
91 no specific function selection is desired for the pins listed in the child
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | imx-audmux.txt | 11 An initial configuration can be setup using child nodes.
13 Required properties of optional child nodes:
16 child node.
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | arm,pl172.txt | 23 - clock-ranges: Empty property indicating that child nodes can inherit
28 Child chip-select (cs) nodes contain the memory devices nodes connected to
31 Required child cs node properties:
37 - ranges: Empty property indicating that child nodes can inherit
40 - clock-ranges: Empty property indicating that child nodes can inherit
50 Optional child cs node config properties:
65 Optional child cs node timing properties:
|
| /Documentation/devicetree/bindings/spmi/ |
| D | spmi.yaml | 20 Each SPMI controller has zero or more child nodes (up to 16 ones), each
38 description: up to 16 child PMIC nodes
70 child@0 {
74 child@7 {
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-mt6323.txt | 19 Each led is represented as a child node of the mediatek,mt6323-led that
21 LED child nodes can be supported.
23 Required properties for the LED child node:
26 Optional properties for the LED child node:
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | sensor-groups.txt | 7 servers. Each child node indicates a sensor group.
11 Each child node contains below properties:
22 - sensors : Phandle array of child nodes of /ibm,opal/sensor/
|
| /Documentation/devicetree/bindings/mmc/ |
| D | amlogic,meson-mx-sdio.txt | 24 Required child nodes:
26 NOTE: due to a driver limitation currently only one slot (= child node)
29 Required properties on each child node (= slot):
33 Optional properties on each child node (= slot):
|
| /Documentation/devicetree/bindings/dma/xilinx/ |
| D | xilinx_dma.txt | 28 - dma-channel child node: Should have at least one channel and can have up to
30 DMA channel (see child node properties below).
59 Required child node properties:
70 Optional child node properties:
73 Optional child node properties for VDMA:
78 Optional child node properties for MCDMA:
79 - dma-channels: Number of dma channels in child node.
|
| /Documentation/devicetree/bindings/media/i2c/ |
| D | adp1653.txt | 12 represented by one child node, nodes need to be named "flash" and "indicator".
14 Required properties of the LED child node:
17 Required properties of the flash LED child node:
|
| /Documentation/devicetree/ |
| D | of_unittest.rst | 71 struct device_node *child;
77 considering only child and sibling pointers. There exists another pointer,
79 a particular level the child node and all the sibling nodes will have a parent
140 In the function of_attach_node(), the new node is attached as the child of the
141 given parent in live tree. But, if parent already has a child then the new node
142 replaces the current child and turns it into its sibling. So, when the testcase
184 test-child0 the test-sibling1 is attached that pushes the child node
185 (i.e. test-child0) to become a sibling and makes itself a child node,
203 To detach a node, of_detach_node() either updates the child pointer of given
|
12345678910>>...22