Home
last modified time | relevance | path

Searched refs:subnodes (Results 1 – 82 of 82) sorted by relevance

/linux-4.4.14/Documentation/devicetree/bindings/phy/
Drcar-gen2-phy.txt11 - #address-cells: number of address cells for the USB channel subnodes, must
13 - #size-cells: number of size cells for the USB channel subnodes, must be <0>.
17 The USB PHY device tree node should have the subnodes corresponding to the USB
18 channels. These subnodes must contain the following properties:
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dqcom,apq8016-sbc.txt19 Dai-link subnode properties and subnodes:
21 Required dai-link subnodes:
26 Required CPU/CODEC subnodes properties:
Dsimple-card.txt26 Optional subnodes:
35 Dai-link subnode properties and subnodes:
41 Required dai-link subnodes:
70 Required CPU/CODEC subnodes properties:
74 Optional CPU/CODEC subnodes properties:
Drenesas,rsrc-card.txt40 Required CPU/CODEC subnodes properties:
44 Optional CPU/CODEC subnodes properties:
/linux-4.4.14/Documentation/devicetree/bindings/pinctrl/
Dqcom,apq8064-pinctrl.txt22 subnodes. Each of these subnodes represents some desired configuration for a
27 The name of each subnode is not important; all subnodes should be enumerated
43 Non-empty subnodes must specify the 'pins' property.
Dpinctrl-sirf.txt16 SiRFprimaII's pinmux nodes act as a container for an arbitrary number of subnodes.
17 Each of these subnodes represents some desired configuration for a group of pins.
28 For example, pinctrl might have subnodes like the following:
Dpinctrl-atlas7.txt63 SiRFatlas7's pinmux nodes act as a container for an abitrary number of subnodes.
64 Each of these subnodes represents some desired configuration for a group of pins.
75 For example, pinctrl might have subnodes like the following:
Dqcom,msm8660-pinctrl.txt22 subnodes. Each of these subnodes represents some desired configuration for a
27 The name of each subnode is not important; all subnodes should be enumerated
43 Non-empty subnodes must specify the 'pins' property.
Dqcom,ipq8064-pinctrl.txt22 subnodes. Each of these subnodes represents some desired configuration for a
27 The name of each subnode is not important; all subnodes should be enumerated
43 Non-empty subnodes must specify the 'pins' property.
Dqcom,msm8974-pinctrl.txt22 subnodes. Each of these subnodes represents some desired configuration for a
27 The name of each subnode is not important; all subnodes should be enumerated
41 Non-empty subnodes must specify the 'pins' property.
Dste,nomadik.txt15 subnodes. Each of these subnodes represents some desired configuration for a
20 The name of each subnode is not important; all subnodes should be enumerated
21 and processed purely based on their content. The subnodes use the generic
Dfsl,imx27-pinctrl.txt6 The iomuxc driver node should define subnodes containing of pinctrl configuration subnodes.
57 node. If gpio subnodes are defined "#address-cells", "#size-cells" and "ranges"
Dlantiq,pinctrl-falcon.txt13 subnodes. Each of these subnodes represents some desired configuration for a
18 The name of each subnode is not important as long as it is unique; all subnodes
Dpinctrl-palmas.txt17 subnodes. Each of these subnodes represents some desired configuration for a
22 The name of each subnode is not important; all subnodes should be enumerated
Dxlnx,zynq-pinctrl.txt13 subnodes. Each of these subnodes represents some desired configuration for a
21 The name of each subnode is not important; all subnodes should be enumerated
Dlantiq,pinctrl-xway.txt13 subnodes. Each of these subnodes represents some desired configuration for a
18 The name of each subnode is not important as long as it is unique; all subnodes
Dimg,tz1090-pdc-pinctrl.txt13 of subnodes. Each of these subnodes represents some desired configuration for a
18 The name of each subnode is not important; all subnodes should be enumerated
Dpinctrl_spear.txt35 SPEAr's pinmux nodes act as a container for an arbitrary number of subnodes. Each
36 of these subnodes represents muxing for a pin, a group, or a list of pins or
39 The name of each subnode is not important; all subnodes should be enumerated
Dqcom,msm8960-pinctrl.txt51 subnodes. Each of these subnodes represents some desired configuration for a
59 The name of each subnode is not important; all subnodes should be enumerated
Dqcom,apq8084-pinctrl.txt51 subnodes. Each of these subnodes represents some desired configuration for a
59 The name of each subnode is not important; all subnodes should be enumerated
Dqcom,msm8916-pinctrl.txt51 subnodes. Each of these subnodes represents some desired configuration for a
59 The name of each subnode is not important; all subnodes should be enumerated
Dqcom,pmic-mpp.txt51 subnodes. Each of these subnodes represents some desired configuration for a
58 The name of each subnode is not important; all subnodes should be enumerated
Dqcom,pmic-gpio.txt50 subnodes. Each of these subnodes represents some desired configuration for a
58 The name of each subnode is not important; all subnodes should be enumerated
Dfsl,mxs-pinctrl.txt17 subnodes. Each of these subnodes represents some desired configuration for
25 Those subnodes under mxs pin controller node will fall into two categories.
Dnvidia,tegra20-pinmux.txt13 subnodes. Each of these subnodes represents some desired configuration for a
18 The name of each subnode is not important; all subnodes should be enumerated
Dpinctrl-mt65xx.txt11 - pins-are-numbered: Specify the subnodes are using numbered pinmux to
41 A pinctrl node should contain at least one subnodes representing the
Dnvidia,tegra124-xusb-padctl.txt35 they should be assigned to. The name of these subnodes is not important. All
36 subnodes should be parsed solely based on their content.
Dnvidia,tegra210-pinmux.txt14 subnodes. Each of these subnodes represents some desired configuration for a
19 The name of each subnode is not important; all subnodes should be enumerated
Dberlin,pinctrl.txt9 A pin-controller node should contain subnodes representing the pin group
Dimg,tz1090-pinctrl.txt13 subnodes. Each of these subnodes represents some desired configuration for a
18 The name of each subnode is not important; all subnodes should be enumerated
Dbrcm,cygnus-pinmux.txt15 Properties in subnodes:
Drenesas,pfc-pinctrl.txt48 or grouped in child subnodes. Both pin muxing and configuration parameters can
57 All pin configuration nodes and subnodes names are ignored. All of those nodes
Dallwinner,sunxi-pinctrl.txt28 A pinctrl node should contain at least one subnodes representing the
Dcnxt,cx92755-pinctrl.txt37 container of an arbitrary number of subnodes, called pin group nodes in this
Dnvidia,tegra114-pinmux.txt15 Tegra114 adds the following optional properties for pin configuration subnodes:
Dnvidia,tegra30-pinmux.txt13 Tegra30 adds the following optional properties for pin configuration subnodes:
Dnvidia,tegra124-pinmux.txt16 Tegra124 adds the following optional properties for pin configuration subnodes.
Dbrcm,bcm11351-pinctrl.txt28 container of an arbitrary number of subnodes, called pin group nodes in this
/linux-4.4.14/scripts/dtc/
Ddtc-parser.y84 %type <nodelist> subnodes
180 '{' proplist subnodes '}' ';'
440 subnodes:
445 | subnode subnodes
Ddtc-parser.tab.c_shipped525 "integer_unary", "bytestring", "subnodes", "subnode", YY_NULLPTR
1984 ERROR(&(yylsp[0]), "Properties must precede subnodes");
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dpartition.txt11 Partitions are then defined in subnodes of the partitions node.
13 For backwards compatibility partitions as direct subnodes of the mtd device are
15 NOTE: also for backwards compatibility, direct subnodes that have a compatible
Dlpc32xx-mlc.txt21 Optional subnodes:
Dlpc32xx-slc.txt22 Optional subnodes:
Dbrcm,brcmnand.txt44 - #address-cells : <1> - subnodes give the chip-select number
85 Each controller (compatible: "brcm,brcmnand") may contain one or more subnodes
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dmfd.txt21 consider all subnodes of the MFD device as separate devices akin to how
22 "simple-bus" inidicates when to see subnodes as children for a simple
Dmt6397.txt20 Optional subnodes:
Dqcom-pm8xxx.txt54 The below bindings specify the set of valid subnodes.
Dqcom-rpm.txt48 The RPM exposes resources to its subnodes. The below bindings specify the set
49 of valid subnodes that can operate on these resources.
Das3722.txt53 nodes contains different subnodes to represents some desired
102 The subnodes name is the name of regulator and it must be one of:
Drk808.txt51 Standard regulator bindings are used inside regulator subnodes. Check
Dmax8998.txt78 Standard regulator bindings are used inside regulator subnodes. Check
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dsnps-dwapb-gpio.txt6 - #address-cells : should be 1 (for addressing port subnodes).
7 - #size-cells : should be 0 (port subnodes).
Dgpio-tz1090.txt9 - #address-cells: Should be 1 (for bank subnodes)
11 - #size-cells: Should be 0 (for bank subnodes)
/linux-4.4.14/drivers/acpi/
Dproperty.c59 INIT_LIST_HEAD(&dn->data.subnodes); in acpi_nondev_subnode_ok()
144 return acpi_add_nondev_subnodes(scope, links, &data->subnodes); in acpi_enumerate_nondev_subnodes()
272 INIT_LIST_HEAD(&adev->data.subnodes); in acpi_init_properties()
317 acpi_destroy_nondev_subnodes(&dn->data.subnodes); in acpi_destroy_nondev_subnodes()
327 acpi_destroy_nondev_subnodes(&adev->data.subnodes); in acpi_free_properties()
832 head = &adev->data.subnodes; in acpi_get_next_subnode()
Ddevice_sysfs.c96 struct list_head *list = &data->subnodes; in acpi_expose_nondev_subnodes()
117 struct list_head *list = &data->subnodes; in acpi_hide_nondev_subnodes()
/linux-4.4.14/Documentation/devicetree/bindings/display/
Dwm,wm8505-fb.txt9 Required subnodes:
Dvia,vt8500-fb.txt10 Required subnodes:
/linux-4.4.14/Documentation/devicetree/bindings/soc/
Dqcom,smd-rpm.txt21 The RPM exposes resources to its subnodes. The below bindings specify the set
22 of valid subnodes that can operate on these resources.
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Darizona-regulator.txt13 Optional subnodes:
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dmmc.txt87 Use of Function subnodes
91 properties. These can be specified in subnodes to the host controller node.
92 The subnodes are identified by the standard 'reg' property.
96 Required host node properties when using function subnodes:
Dmmc-card.txt5 child node describing a mmc-card / an eMMC, see "Use of Function subnodes"
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dvexpress-sysreg.txt12 Deprecated properties, replaced by GPIO subnodes (see below):
22 by subnodes, each of them requiring the following properties:
Datmel-at91.txt56 Its subnodes can be:
Dtopology.txt58 subnodes describe the CPU topology.
Dcpus.txt6 the "cpus" node, which in turn contains a number of subnodes (ie "cpu")
Didle-states.txt222 subnodes describe the CPU idle states.
/linux-4.4.14/Documentation/devicetree/bindings/arm/ux500/
Dboards.txt16 Required subnodes under soc node:
/linux-4.4.14/Documentation/devicetree/bindings/net/
Dmarvell-pp2.txt16 The ethernet ports are represented by subnodes. At least one port is
Dfsl-fec.txt28 Optional subnodes:
/linux-4.4.14/Documentation/devicetree/bindings/soc/sunxi/
Dsram.txt22 SRAM controller as subnodes. These sections are represented following
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Dux500.txt12 Required subnodes:
/linux-4.4.14/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smd.txt48 In turn, subnodes of the "edges" represent devices tied to SMD channels on that
/linux-4.4.14/Documentation/devicetree/bindings/soc/fsl/
Dqman-portals.txt67 These subnodes should have the following properties:
/linux-4.4.14/Documentation/devicetree/bindings/net/dsa/
Ddsa.txt66 Optional subnodes:
/linux-4.4.14/Documentation/devicetree/bindings/arm/tegra/
Dnvidia,tegra20-emc.txt47 subnodes of the emc controller node.
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/
Dtegra-emc.txt18 EMC clock rate. The "timing" subnodes should have the clock rate in Hz as
/linux-4.4.14/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,brcmstb.txt159 Should contain subnodes for any of the following relevant hardware resources:
/linux-4.4.14/include/acpi/
Dacpi_bus.h346 struct list_head subnodes; member
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dnvidia,tegra20-pcie.txt110 Root ports are defined as subnodes of the PCIe controller node.
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dvideo-interfaces.txt16 transfer and is described by 'endpoint' subnodes.
/linux-4.4.14/Documentation/i2c/
Dinstantiating-devices58 devices is here done via devicetree as subnodes of the master controller.
/linux-4.4.14/Documentation/devicetree/
Dbooting-without-of.txt672 subnodes were intermingled, the kernel parser requires that the