| /linux-4.1.27/Documentation/devicetree/bindings/sound/ |
| D | simple-card.txt | 34 Dai-link subnode properties and subnodes:
36 If dai-link subnode is omitted and the subnode properties are directly
37 under "sound"-node the subnode property and subnode names have to be
45 Optional dai-link subnode properties:
51 phandle to a cpu or codec subnode.
53 phandle to a cpu or codec subnode.
60 properties can be used as booleans in codec subnode to indicate if the
74 - clocks / system-clock-frequency : specify subnode's clock if needed.
|
| D | renesas,rsrc-card.txt | 18 Optional subnode properties:
24 phandle to a cpu or codec subnode.
26 phandle to a cpu or codec subnode.
39 - clocks / system-clock-frequency : specify subnode's clock if needed.
|
| D | renesas,rsnd.txt | 15 The number of SSI subnode should be same as HW.
18 The number of SRC subnode should be same as HW.
21 The number of DVC subnode should be same as HW.
24 The number of DAI subnode should be same as HW.
27 SSI subnode properties:
36 SRC subnode properties:
40 DVC subnode properties:
44 DAI subnode properties:
|
| /linux-4.1.27/Documentation/devicetree/bindings/pinctrl/ |
| D | lantiq,falcon-pinumx.txt | 18 The name of each subnode is not important as long as it is unique; all subnodes
21 Each subnode only affects those parameters that are explicitly listed. In
22 other words, a subnode that lists a mux function but no pin configuration
24 Similarly, a pin subnode that describes a pullup parameter implies no
31 Required subnode-properties:
49 Required subnode-properties:
53 Optional subnode-properties:
|
| D | lantiq,xway-pinumx.txt | 18 The name of each subnode is not important as long as it is unique; all subnodes
21 Each subnode only affects those parameters that are explicitly listed. In
22 other words, a subnode that lists a mux function but no pin configuration
24 Similarly, a pin subnode that describes a pullup parameter implies no
31 Required subnode-properties:
56 Required subnode-properties:
60 Optional subnode-properties:
|
| D | pinctrl-vt8500.txt | 25 configuration. Each subnode only affects those parameters that are explicitly
26 listed. In other words, a subnode that lists only a mux function implies no
27 information about any pull configuration. Similarly, a subnode that lists only
30 Required subnode-properties:
33 Optional subnode-properties:
|
| D | brcm,bcm2835-gpio.txt | 34 configuration. Each subnode only affects those parameters that are explicitly
35 listed. In other words, a subnode that lists only a mux function implies no
36 information about any pull configuration. Similarly, a subnode that lists only
39 Required subnode-properties:
43 Optional subnode-properties:
|
| D | qcom,apq8064-pinctrl.txt | 27 The name of each subnode is not important; all subnodes should be enumerated
30 Each subnode only affects those parameters that are explicitly listed. In
31 other words, a subnode that lists a mux function but no pin configuration
33 Similarly, a pin subnode that describes a pullup parameter implies no
38 to specify in a pin configuration subnode:
|
| D | qcom,ipq8064-pinctrl.txt | 27 The name of each subnode is not important; all subnodes should be enumerated
30 Each subnode only affects those parameters that are explicitly listed. In
31 other words, a subnode that lists a mux function but no pin configuration
33 Similarly, a pin subnode that describes a pullup parameter implies no
38 to specify in a pin configuration subnode:
|
| D | img,tz1090-pdc-pinctrl.txt | 18 The name of each subnode is not important; all subnodes should be enumerated
21 Each subnode only affects those parameters that are explicitly listed. In
22 other words, a subnode that lists a mux function but no pin configuration
24 Similarly, a pin subnode that describes a pullup parameter implies no
30 Required subnode-properties:
34 Optional subnode-properties:
|
| D | qcom,pmic-mpp.txt | 53 The name of each subnode is not important; all subnodes should be enumerated
56 Each subnode only affects those parameters that are explicitly listed. In
57 other words, a subnode that lists a mux function but no pin configuration
59 Similarly, a pin subnode that describes a pullup parameter implies no
63 to specify in a pin configuration subnode:
69 this subnode. Valid pins are:
|
| D | qcom,msm8974-pinctrl.txt | 27 The name of each subnode is not important; all subnodes should be enumerated
30 Each subnode only affects those parameters that are explicitly listed. In
31 other words, a subnode that lists a mux function but no pin configuration
33 Similarly, a pin subnode that describes a pullup parameter implies no
38 to specify in a pin configuration subnode:
|
| D | qcom,apq8084-pinctrl.txt | 59 The name of each subnode is not important; all subnodes should be enumerated
62 Each subnode only affects those parameters that are explicitly listed. In
63 other words, a subnode that lists a mux function but no pin configuration
65 Similarly, a pin subnode that describes a pullup parameter implies no
70 to specify in a pin configuration subnode:
76 this subnode. Valid pins are:
|
| D | qcom,msm8960-pinctrl.txt | 59 The name of each subnode is not important; all subnodes should be enumerated
62 Each subnode only affects those parameters that are explicitly listed. In
63 other words, a subnode that lists a mux function but no pin configuration
65 Similarly, a pin subnode that describes a pullup parameter implies no
70 to specify in a pin configuration subnode:
76 this subnode. Valid pins are:
|
| D | qcom,msm8916-pinctrl.txt | 59 The name of each subnode is not important; all subnodes should be enumerated
62 Each subnode only affects those parameters that are explicitly listed. In
63 other words, a subnode that lists a mux function but no pin configuration
65 Similarly, a pin subnode that describes a pullup parameter implies no
70 to specify in a pin configuration subnode:
76 this subnode. Valid pins are:
|
| D | allwinner,sunxi-pinctrl.txt | 26 pinctrl groups available on the machine. Each subnode will list the
31 Required subnode-properties:
36 Optional subnode-properties:
|
| D | qcom,pmic-gpio.txt | 58 The name of each subnode is not important; all subnodes should be enumerated
61 Each subnode only affects those parameters that are explicitly listed. In
62 other words, a subnode that lists a mux function but no pin configuration
64 Similarly, a pin subnode that describes a pullup parameter implies no
68 to specify in a pin configuration subnode:
74 this subnode. Valid pins are:
|
| D | xlnx,zynq-pinctrl.txt | 21 The name of each subnode is not important; all subnodes should be enumerated
35 to specify in a pinmux subnode:
39 to specify in a pinconf subnode:
68 a pin configuration subnode:
|
| D | pinctrl-palmas.txt | 22 The name of each subnode is not important; all subnodes should be enumerated
25 Each subnode only affects those parameters that are explicitly listed. In
26 other words, a subnode that lists a mux function but no pin configuration
28 Similarly, a pin subnode that describes a pullup parameter implies no
|
| D | nvidia,tegra20-pinmux.txt | 18 The name of each subnode is not important; all subnodes should be enumerated
21 Each subnode only affects those parameters that are explicitly listed. In
22 other words, a subnode that lists a mux function but no pin configuration
24 Similarly, a pin subnode that describes a pullup parameter implies no
30 Required subnode-properties:
34 Optional subnode-properties:
|
| D | nvidia,tegra124-xusb-padctl.txt | 34 Each subnode describes groups of lanes along with parameters and pads that
38 Each subnode only applies the parameters that are explicitly listed. In other
39 words, if a subnode that lists a function but no pin configuration parameters
41 subnode that describes only an IDDQ parameter implies no information about
|
| D | nvidia,tegra210-pinmux.txt | 19 The name of each subnode is not important; all subnodes should be enumerated
22 Each subnode only affects those parameters that are explicitly listed. In
23 other words, a subnode that lists a mux function but no pin configuration
25 Similarly, a pin subnode that describes a pullup parameter implies no
35 Required subnode-properties:
39 Optional subnode-properties:
|
| D | img,tz1090-pinctrl.txt | 18 The name of each subnode is not important; all subnodes should be enumerated
21 Each subnode only affects those parameters that are explicitly listed. In
22 other words, a subnode that lists a mux function but no pin configuration
24 Similarly, a pin subnode that describes a pullup parameter implies no
30 Required subnode-properties:
34 Optional subnode-properties:
|
| D | ste,nomadik.txt | 18 The name of each subnode is not important; all subnodes should be enumerated
23 Required pin multiplexing subnode properties:
30 Required pin configuration subnode properties:
|
| D | fsl,mxs-pinctrl.txt | 19 In other words, a subnode that describes a drive strength parameter implies no
41 Required subnode-properties:
60 Optional subnode-properties:
|
| D | pinctrl_spear.txt | 39 The name of each subnode is not important; all subnodes should be enumerated
42 Required subnode-properties:
|
| D | pinctrl-sirf.txt | 19 Required subnode-properties:
|
| D | abilis,tb10x-iomux.txt | 21 Required function definition subnode properties:
|
| D | pinctrl-mt65xx.txt | 37 pinctrl groups available on the machine. Each subnode will list the
|
| D | pinctrl-st.txt | 102 Contents of function subnode node:
|
| D | renesas,pfc-pinctrl.txt | 49 A configuration node or subnode must reference at least one pin (through the
|
| D | pinctrl-single.txt | 74 range. They're value of subnode phandle, pin base in pinctrl device, pin
|
| /linux-4.1.27/arch/ia64/include/asm/sn/ |
| D | sn_cpuid.h | 95 #define get_subnode() (sn_nodepda->phys_cpuid[smp_processor_id()].subnode)
105 #define cpuid_to_subnode(cpuid) (sn_nodepda->phys_cpuid[cpuid].subnode)
|
| D | nodepda.h | 33 char subnode; member
|
| D | sn_sal.h | 1006 ia64_sn_get_sapic_info(int sapicid, int *nasid, int *subnode, int *slice) in ia64_sn_get_sapic_info() argument
1019 if (subnode) *subnode = (sapicid >> 13) & 1; in ia64_sn_get_sapic_info()
1029 if (subnode) *subnode = (int) ret_stuff.v1; in ia64_sn_get_sapic_info()
|
| /linux-4.1.27/scripts/dtc/ |
| D | dtc-parser.y | 88 %type <node> subnode
444 | subnode subnodes
448 | subnode propdef
455 subnode:
464 | DT_LABEL subnode
|
| D | livetree.c | 672 struct node *subnode, **tbl; in sort_subnodes() local
674 for_each_child_withdel(node, subnode) in sort_subnodes()
682 for_each_child_withdel(node, subnode) in sort_subnodes()
683 tbl[i++] = subnode; in sort_subnodes()
|
| D | dtc-parser.tab.c_shipped | 561 "integer_unary", "bytestring", "subnodes", "subnode", YY_NULL
|
| /linux-4.1.27/Documentation/devicetree/bindings/gpio/ |
| D | gpio-tz1090.txt | 13 - Each bank of GPIOs should have a subnode to represent it.
15 Bank subnode required properties:
33 Bank subnode optional properties:
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/st/ |
| D | st,clkgen.txt | 7 address is common of all subnode.
43 Each subnode should use the binding discribe in [2]..[7]
|
| /linux-4.1.27/arch/ia64/sn/kernel/ |
| D | setup.c | 566 int subnode; in sn_cpu_init() local
619 if (ia64_sn_get_sapic_info(cpuphyid, &nasid, &subnode, &slice)) in sn_cpu_init()
626 nodepdaindr[i]->phys_cpuid[cpuid].subnode = subnode; in sn_cpu_init()
|
| /linux-4.1.27/Documentation/devicetree/bindings/power_supply/ |
| D | charger-manager.txt | 10 - subnode <regulator> :
12 - subnode <cable> :
|
| D | tps65090.txt | 10 This node is a subnode of the tps65090 PMIC.
|
| /linux-4.1.27/Documentation/devicetree/bindings/mmc/ |
| D | mmc.txt | 87 SDIO function driver for the subnode, as specified by the compatible string.
93 Required function subnode properties:
95 - reg: Must contain the SDIO function number of the function this subnode
119 Example with sdio function subnode:
|
| /linux-4.1.27/Documentation/devicetree/bindings/media/ |
| D | samsung-s5c73m3.txt | 38 device node should contain one 'port' child node with an 'endpoint' subnode for
45 endpoint subnode
|
| D | samsung-s5k6a3.txt | 28 node should contain one 'port' child node with an 'endpoint' subnode.
|
| D | exynos4-fimc-is.txt | 23 pmu subnode
|
| D | video-interfaces.txt | 45 phandles. An endpoint subnode of a device contains all properties needed for
73 - remote-endpoint: phandle to an 'endpoint' subnode of a remote device node.
|
| /linux-4.1.27/Documentation/devicetree/bindings/clock/ |
| D | arm-integrator.txt | 9 This clock node *must* be a subnode of the core module, since
|
| /linux-4.1.27/Documentation/devicetree/bindings/input/ |
| D | gpio-keys-polled.txt | 18 Optional subnode-properties:
|
| D | sun4i-lradc-keys.txt | 12 Required subnode-properties:
|
| D | gpio-keys.txt | 21 Optional subnode-properties:
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/ |
| D | hisilicon-hix5hd2-gmac.txt | 16 - PHY subnode: inherits from phy binding [2]
|
| D | altera_tse.txt | 35 - mdio device tree subnode: When the TSE has a phy connected to its local
36 mdio, there must be device tree subnode with the following
|
| D | brcm,bcm7445-switch-v4.0.txt | 16 The integrated switch subnode should be specified according to the binding
|
| D | apm-xgene-enet.txt | 29 - mdio: Device tree subnode with the following required properties:
|
| /linux-4.1.27/Documentation/devicetree/bindings/usb/ |
| D | keystone-usb.txt | 19 The dwc3 core should be added as subnode to Keystone DWC3 glue.
|
| D | dwc3.txt | 42 This is usually a subnode to DWC3 glue to which it is connected.
|
| D | dwc3-st.txt | 32 The dwc3 core should be added as subnode to ST DWC3 glue as shown in the
|
| D | omap-usb.txt | 65 The dwc3 core should be added as subnode to omap dwc3 glue.
|
| D | exynos-usb.txt | 97 The dwc3 core should be added as subnode to Exynos dwc3 glue.
|
| /linux-4.1.27/Documentation/devicetree/bindings/phy/ |
| D | ti-phy.txt | 47 This is usually a subnode of ocp2scp to which it is connected.
86 This is usually a subnode of ocp2scp to which it is connected.
|
| /linux-4.1.27/Documentation/devicetree/bindings/ |
| D | graph.txt | 31 Each port node contains an 'endpoint' subnode for each remote device port
128 - remote-endpoint: phandle to an 'endpoint' subnode of a remote device node.
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/ |
| D | marvell,berlin.txt | 99 configurations, one per function. Each subnode has the group name and the muxing
105 Required subnode-properties:
|
| D | arm-boards | 124 - syscon: some subnode of the RealView SoC node must be a
|
| /linux-4.1.27/Documentation/devicetree/bindings/video/ |
| D | display-timing.txt | 14 timing subnode
|
| /linux-4.1.27/Documentation/devicetree/bindings/mfd/ |
| D | qcom-pm8xxx.txt | 53 The PMIC contains multiple independent functions, each described in a subnode.
|
| D | max77686.txt | 21 under subnode named "voltage-regulators" using the following format.
|
| D | as3722.txt | 59 Each subnode have following properties:
82 Following are properties of regulator subnode.
|
| D | as3711.txt | 6 configuration should be placed in a subnode, called "backlight."
|
| /linux-4.1.27/Documentation/devicetree/bindings/regulator/ |
| D | as3722-regulator.txt | 2 Name of the regulator subnode must be "regulators".
|
| D | max77802.txt | 13 under subnode named "regulators" using the following format.
|
| /linux-4.1.27/Documentation/devicetree/bindings/net/dsa/ |
| D | dsa.txt | 62 - fixed-link : Fixed-link subnode describing a link to a non-MDIO
|
| /linux-4.1.27/Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra20-pmc.txt | 55 On Tegra30, Tegra114 and Tegra124, if the 'i2c-thermtrip' subnode exists,
|
| /linux-4.1.27/Documentation/devicetree/ |
| D | booting-without-of.txt | 670 a particular node MUST precede any subnode definitions for that node.
|