| /Documentation/translations/zh_TW/filesystems/ |
| D | debugfs.rst | 42 struct dentry *debugfs_create_dir(const char *name, struct dentry *parent);
53 struct dentry *parent, void *data,
64 struct dentry *parent, void *data,
74 struct dentry *parent, u8 *value);
76 struct dentry *parent, u16 *value);
78 struct dentry *parent, u32 *value);
80 struct dentry *parent, u64 *value);
87 struct dentry *parent, u8 *value);
89 struct dentry *parent, u16 *value);
91 struct dentry *parent, u32 *value);
[all …]
|
| /Documentation/translations/zh_CN/filesystems/ |
| D | debugfs.rst | 41 struct dentry *debugfs_create_dir(const char *name, struct dentry *parent);
52 struct dentry *parent, void *data,
63 struct dentry *parent, void *data,
73 struct dentry *parent, u8 *value);
75 struct dentry *parent, u16 *value);
77 struct dentry *parent, u32 *value);
79 struct dentry *parent, u64 *value);
86 struct dentry *parent, u8 *value);
88 struct dentry *parent, u16 *value);
90 struct dentry *parent, u32 *value);
[all …]
|
| /Documentation/devicetree/bindings/edac/ |
| D | socfpga-eccmgr.txt | 89 - altr,ecc-parent : phandle to parent Ethernet node.
97 - altr,ecc-parent : phandle to parent NAND node.
105 - altr,ecc-parent : phandle to parent DMA node.
113 - altr,ecc-parent : phandle to parent USB node.
121 - altr,ecc-parent : phandle to parent QSPI node.
129 - altr,ecc-parent : phandle to parent SD/MMC node.
164 altr,ecc-parent = <&gmac0>;
172 altr,ecc-parent = <&gmac0>;
180 altr,ecc-parent = <&nand>;
188 altr,ecc-parent = <&nand>;
[all …]
|
| /Documentation/i2c/ |
| D | i2c-topology.rst | 23 each adapter has a parent adapter (except the root adapter) and zero or
25 I2C transfers, and all adapters with a parent are part of an "i2c-mux"
40 mux-locked or parent-locked muxes.
46 Mux-locked muxes does not lock the entire parent adapter during the
47 full select-transfer-deselect transaction, only the muxes on the parent
50 their tasks. Since the parent adapter is not fully locked during the
72 2. M1 locks muxes on its parent (the root adapter in this case).
75 These transfers are normal I2C transfers that locks the parent
77 5. M1 feeds the I2C transfer from step 1 to its parent adapter as a
78 normal I2C transfer that locks the parent adapter.
[all …]
|
| /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.
52 # mkdir -p /sys/fs/cgroup/pids/parent/child
53 # echo 2 > /sys/fs/cgroup/pids/parent/pids.max
54 # echo $$ > /sys/fs/cgroup/pids/parent/cgroup.procs
55 # cat /sys/fs/cgroup/pids/parent/pids.current
62 # cat /sys/fs/cgroup/pids/parent/pids.current
70 parent's)::
72 # echo $$ > /sys/fs/cgroup/pids/parent/child/cgroup.procs
73 # cat /sys/fs/cgroup/pids/parent/pids.current
[all …]
|
| /Documentation/filesystems/ |
| D | directory-locking.rst | 30 * lock the parent (exclusive)
36 * lock the parent (exclusive)
42 * lock the parent (exclusive)
58 ancestor of the other, lock the parent of source first.
89 dcache trees. Lookup is already holding the parent locked. If alias is
97 current parent of the alias. If either trylock fails, we fail the lookup.
98 If trylocks succeed, we detach the alias from its current parent and
187 only 3 possible operations: directory removal (locks parent, then
192 if all operations had been of the "lock parent, then child" sort
193 we would have Dn a parent of D1, which is a parent of D2, which is
[all …]
|
| D | debugfs.rst | 35 struct dentry *debugfs_create_dir(const char *name, struct dentry *parent);
38 indicated parent directory. If parent is NULL, the directory will be
49 struct dentry *parent, void *data,
53 permissions the file should have, parent indicates the directory which
66 struct dentry *parent, void *data,
79 struct dentry *parent, u8 *value);
81 struct dentry *parent, u16 *value);
83 struct dentry *parent, u32 *value);
85 struct dentry *parent, u64 *value);
93 struct dentry *parent, u8 *value);
[all …]
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | interrupts.txt | 16 interrupt-parent = <&intc1>;
19 The "interrupt-parent" property is used to specify the controller to which
22 interrupt client node or in any of its parent nodes. Interrupts listed in the
23 "interrupts" property are always in reference to the node's interrupt parent.
26 to reference multiple interrupt parents or a different interrupt parent than
27 the inherited one. Each entry in this property contains both the parent phandle
63 interrupt-parent = <&vic>;
85 interrupt-parent = <&gpio>;
101 interrupt-parent = <&gpioext>;
112 3) Interrupt wakeup parent
[all …]
|
| D | marvell,icu.txt | 39 - msi-parent: Should point to the GICP controller, the GIC extension
57 msi-parent = <&gicp>;
65 msi-parent = <&sei>;
70 interrupt-parent = <&icu_nsr>;
75 interrupt-parent = <&icu_sei>;
81 interrupt-parent = <&icu_nsr>;
106 msi-parent = <&gicp>;
110 interrupt-parent = <&icu>;
|
| D | riscv,aplic.yaml | 19 interrupt sources connect to the root APLIC domain and a parent APLIC
47 node, which has a CPU node (i.e. RISC-V HART) as parent.
49 msi-parent:
52 message signaled interrupt controller (IMSIC). If both "msi-parent" and
85 - description: first interrupt number of the parent APLIC domain (inclusive)
86 - description: last interrupt number of the parent APLIC domain (inclusive)
89 of child APLIC domain phandle, first interrupt number of the parent
90 APLIC domain, and last interrupt number of the parent APLIC domain.
108 - msi-parent
155 msi-parent = <&imsic_mlevel>;
[all …]
|
| D | brcm,bcm6345-l1-intc.txt | 32 - interrupts: specifies the interrupt line(s) in the interrupt-parent controller
33 node; valid values depend on the type of parent interrupt controller
35 If multiple reg ranges and interrupt-parent entries are present on an SMP
38 reg range and one interrupt-parent is needed.
53 interrupt-parent = <&cpu_intc>;
|
| D | abilis,tb10x-ictl.txt | 17 the interrupt controller in the parent controller's notation. Interrupts
18 are mapped one-to-one to parent interrupts.
23 intc: interrupt-controller { /* Parent interrupt controller */
34 interrupt-parent = <&intc>;
|
| D | st,spear3xx-shirq.txt | 4 of devices. The multiplexor provides a single interrupt to parent
29 then connected to a parent interrupt controller. Each group is
31 parent) is equal to number of groups. The format of the interrupt
32 specifier depends in the interrupt parent controller.
|
| /Documentation/livepatch/ |
| D | shadow-vars.rst | 7 allocated separately from parent data structures, which are left
12 associates pointers to parent objects and a numeric identifier of the
15 specifically, the parent pointer serves as the hashtable key while the
17 variables may attach to the same parent object, but their numeric
34 - obj - pointer to parent object
107 Matching parent's lifecycle
110 If parent data structures are frequently created and destroyed, it may
112 allocation and release functions. In this case, the parent data
115 part of the parent's initialization and should be completed before the
116 parent "goes live" (ie, any shadow variable get-API requests are made
[all …]
|
| /Documentation/driver-api/ |
| D | dpll.rst | 117 attribute ``DPLL_A_PIN_PARENT_PIN`` for each parent they were registered
119 If a pin was registered with multiple parent pins, they behave like a
121 ``DPLL_CMD_PIN_GET`` would contain multiple pin-parent nested
122 attributes with current state related to each parent, like::
129 'parent-pin': [
130 {'parent-id': 2, 'state': 'connected'},
131 {'parent-id': 3, 'state': 'disconnected'}
136 Only one child pin can provide its signal to the parent MUX-type pin at
138 on desired parent, with the use of ``DPLL_A_PIN_PARENT`` nested
139 attribute. Example of netlink `set state on parent pin` message format:
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | mdio-mux-gpio.yaml | 45 mdio-parent-bus = <&smi1>;
60 interrupt-parent = <&gpio>;
69 interrupt-parent = <&gpio>;
78 interrupt-parent = <&gpio>;
87 interrupt-parent = <&gpio>;
103 interrupt-parent = <&gpio>;
112 interrupt-parent = <&gpio>;
121 interrupt-parent = <&gpio>;
130 interrupt-parent = <&gpio>;
|
| /Documentation/networking/devlink/ |
| D | ice.rst | 41 the 9th queue has a different parent than the rest, and it's given
58 to the same parent in the tree. The obvious drawback of this solution
435 pci/0000:4b:00.0/node_25: type node parent node_24
436 pci/0000:4b:00.0/node_24: type node parent node_0
437 pci/0000:4b:00.0/node_32: type node parent node_31
438 pci/0000:4b:00.0/node_31: type node parent node_30
439 pci/0000:4b:00.0/node_30: type node parent node_16
440 pci/0000:4b:00.0/node_19: type node parent node_18
441 pci/0000:4b:00.0/node_18: type node parent node_17
442 pci/0000:4b:00.0/node_17: type node parent node_16
[all …]
|
| /Documentation/devicetree/bindings/clock/ti/ |
| D | mux.txt | 6 gate or adjust the parent rate via a divider or multiplier.
15 register value selected parent clock
24 register value selected clock parent
39 - clocks : link phandles of parent clocks
48 - ti,set-rate-parent : clk_set_rate is propagated to parent clock,
|
| /Documentation/devicetree/bindings/interconnect/ |
| D | samsung,exynos-bus.yaml | 27 - parent bus device
30 Basically, parent and passive bus device share the same power line. The
31 parent bus device can only change the voltage of shared power line and the
32 rest bus devices (passive bus device) depend on the decision of the parent
34 Only one block should be parent device and then the rest blocks should depend
35 on the parent device as passive device.
37 VDD_xxx |--- A block (parent)
51 VDD_INT |--- LEFTBUS (parent device)
81 |Mode |*parent|passive |passive|passive|passive|| |
93 VDD_INT |--- DMC (parent device, Dynamic Memory Controller)
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-mux-gpmux.yaml | 38 i2c-parent:
52 Explicitly allow unrelated I2C transactions on the parent I2C adapter at
60 to the same parent adapter that this multiplexer is connected to are blocked
63 If mux-locked is not present, the multiplexer is assumed to be parent-locked.
64 This means that no unrelated I2C transactions are allowed on the parent I2C
66 The properties of mux-locked and parent-locked multiplexers are discussed
71 - i2c-parent
90 i2c-parent = <&i2c1>;
|
| /Documentation/devicetree/bindings/sound/ |
| D | ti,j721e-cpb-ivi-audio.yaml | 23 In order to support 48KHz and 44.1KHz family of sampling rates the parent clock
76 - description: Parent for CPB_McASP auxclk (for 48KHz)
77 - description: Parent for CPB_McASP auxclk (for 44.1KHz)
79 - description: Parent for CPB_SCKI clock (for 48KHz)
80 - description: Parent for CPB_SCKI clock (for 44.1KHz)
82 - description: Parent for IVI_McASP auxclk (for 48KHz)
83 - description: Parent for IVI_McASP auxclk (for 44.1KHz)
85 - description: Parent for IVI_SCKI clock (for 48KHz)
86 - description: Parent for IVI_SCKI clock (for 44.1KHz)
|
| D | ti,j721e-cpb-audio.yaml | 18 In order to support 48KHz and 44.1KHz family of sampling rates the parent
85 - description: Parent for CPB_McASP auxclk (for 48KHz)
86 - description: Parent for CPB_McASP auxclk (for 44.1KHz)
88 - description: Parent for CPB_SCKI clock (for 48KHz)
89 - description: Parent for CPB_SCKI clock (for 44.1KHz)
111 - description: Parent for CPB_McASP auxclk (for 48KHz)
113 - description: Parent for CPB_SCKI clock (for 48KHz)
|
| /Documentation/devicetree/bindings/clock/ |
| D | samsung,exynos-audss-clock.yaml | 31 Fixed rate PLL reference clock, parent of mout_audss. "fin_pll" is
34 Input PLL to the AudioSS block, parent of mout_audss. "fout_epll" is
37 Audio bus clock, parent of mout_i2s. "sclk_audio0" is used if not
40 PCM clock, parent of sclk_pcm. "sclk_pcm0" is used if not specified.
42 External i2s clock, parent of mout_i2s. "cdclk0" is used if not
|
| /Documentation/scheduler/ |
| D | sched-domains.rst | 6 hierarchy is built from these base domains via the ->parent pointer. ->parent
42 sched domains our CPU is on, starting from its base domain and going up the ->parent
45 the parent sched_domain (if it exists), and the parent of the parent and so
62 In SMP, the parent of the base domain will span all physical CPUs in the
63 node. Each group being a single physical CPU. Then with NUMA, the parent
|
| /Documentation/devicetree/bindings/mux/ |
| D | reg-mux.yaml | 13 Define register bitfields to be used to control multiplexers. The parent
19 - reg-mux # parent device of mux controller is not syscon device
20 - mmio-mux # parent device of mux controller is syscon device
46 /* The parent device of mux controller is not a syscon device. */
61 mdio-parent-bus = <&emdio1>;
81 mdio-parent-bus = <&emdio2>;
99 /* The parent device of mux controller is syscon device. */
|