Home
last modified time | relevance | path

Searched full:subnode (Results 1 – 25 of 326) sorted by relevance

12345678910>>...14

/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/pinctrl/
H A Dlantiq,pinctrl-falcon.txt18 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:
H A Dpinctrl-vt8500.txt25 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:
H A Daxis,artpec6-pinctrl.txt8 A pinctrl node should contain at least one subnode representing the pinctrl
9 groups available on the machine. Each subnode will list the mux function
10 required and what pin group it will use. Each subnode will also configure the
15 Required subnode-properties:
49 Optional subnode-properties (see pinctrl-bindings.txt):
H A Dqcom,mdm9615-pinctrl.txt67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
H A Dqcom,ipq8064-pinctrl.txt32 The name of each subnode is not important; all subnodes should be enumerated
35 Each subnode only affects those parameters that are explicitly listed. In
36 other words, a subnode that lists a mux function but no pin configuration
38 Similarly, a pin subnode that describes a pullup parameter implies no
43 to specify in a pin configuration subnode:
H A Dqcom,apq8064-pinctrl.txt32 The name of each subnode is not important; all subnodes should be enumerated
35 Each subnode only affects those parameters that are explicitly listed. In
36 other words, a subnode that lists a mux function but no pin configuration
38 Similarly, a pin subnode that describes a pullup parameter implies no
43 to specify in a pin configuration subnode:
H A Dqcom,ipq4019-pinctrl.txt35 The name of each subnode is not important; all subnodes should be enumerated
38 Each subnode only affects those parameters that are explicitly listed. In
39 other words, a subnode that lists a mux function but no pin configuration
41 Similarly, a pin subnode that describes a pullup parameter implies no
46 to specify in a pin configuration subnode:
H A Dqcom,msm8660-pinctrl.txt32 The name of each subnode is not important; all subnodes should be enumerated
35 Each subnode only affects those parameters that are explicitly listed. In
36 other words, a subnode that lists a mux function but no pin configuration
38 Similarly, a pin subnode that describes a pullup parameter implies no
43 to specify in a pin configuration subnode:
H A Dqcom,msm8960-pinctrl.txt67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
H A Dqcom,ipq8074-pinctrl.txt67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
H A Dqcom,msm8976-pinctrl.txt67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode.
H A Dqcom,sdm845-pinctrl.txt59 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.
H A Dqcom,pmic-mpp.txt65 The name of each subnode is not important; all subnodes should be enumerated
68 Each subnode only affects those parameters that are explicitly listed. In
69 other words, a subnode that lists a mux function but no pin configuration
71 Similarly, a pin subnode that describes a pullup parameter implies no
75 to specify in a pin configuration subnode:
81 this subnode. Valid pins are:
H A Dqcom,apq8084-pinctrl.txt67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode. Valid pins are:
H A Dbrcm,bcm2835-gpio.txt41 configuration. Each subnode only affects those parameters that are explicitly
42 listed. In other words, a subnode that lists only a mux function implies no
43 information about any pull configuration. Similarly, a subnode that lists only
64 Required subnode-properties:
68 Optional subnode-properties:
H A Dqcom,sm8150-pinctrl.txt76 The name of each subnode is not important; all subnodes should be enumerated
79 Each subnode only affects those parameters that are explicitly listed. In
80 other words, a subnode that lists a mux function but no pin configuration
82 Similarly, a pin subnode that describes a pullup parameter implies no
87 to specify in a pin configuration subnode:
93 this subnode.
H A Dqcom,msm8994-pinctrl.txt69 The name of each subnode is not important; all subnodes should be enumerated
72 Each subnode only affects those parameters that are explicitly listed. In
73 other words, a subnode that lists a mux function but no pin configuration
75 Similarly, a pin subnode that describes a pullup parameter implies no
80 to specify in a pin configuration subnode:
86 this subnode.
H A Dqcom,msm8998-pinctrl.txt67 The name of each subnode is not important; all subnodes should be enumerated
70 Each subnode only affects those parameters that are explicitly listed. In
71 other words, a subnode that lists a mux function but no pin configuration
73 Similarly, a pin subnode that describes a pullup parameter implies no
78 to specify in a pin configuration subnode:
84 this subnode.
/OK3568_Linux_fs/u-boot/drivers/power/pmic/
H A Dpalmas.c50 ofnode subnode; in palmas_bind() local
53 dev_for_each_subnode(subnode, dev) { in palmas_bind()
57 name = ofnode_get_name(subnode); in palmas_bind()
60 pmic_node = subnode; in palmas_bind()
66 debug("%s: %s pmic subnode not found!", __func__, dev->name); in palmas_bind()
73 debug("%s: %s reg subnode not found!", __func__, dev->name); in palmas_bind()
/OK3568_Linux_fs/u-boot/drivers/spi/
H A Dcadence_qspi.c286 int subnode; in cadence_spi_ofdata_to_platdata() local
306 subnode = fdt_first_subnode(blob, node); in cadence_spi_ofdata_to_platdata()
307 if (subnode < 0) { in cadence_spi_ofdata_to_platdata()
308 printf("Error: subnode with SPI flash config missing!\n"); in cadence_spi_ofdata_to_platdata()
313 plat->max_hz = fdtdec_get_uint(blob, subnode, "spi-max-frequency", in cadence_spi_ofdata_to_platdata()
317 plat->page_size = fdtdec_get_uint(blob, subnode, "page-size", 256); in cadence_spi_ofdata_to_platdata()
318 plat->block_size = fdtdec_get_uint(blob, subnode, "block-size", 16); in cadence_spi_ofdata_to_platdata()
319 plat->tshsl_ns = fdtdec_get_uint(blob, subnode, "cdns,tshsl-ns", 200); in cadence_spi_ofdata_to_platdata()
320 plat->tsd2d_ns = fdtdec_get_uint(blob, subnode, "cdns,tsd2d-ns", 255); in cadence_spi_ofdata_to_platdata()
321 plat->tchsh_ns = fdtdec_get_uint(blob, subnode, "cdns,tchsh-ns", 20); in cadence_spi_ofdata_to_platdata()
[all …]
/OK3568_Linux_fs/u-boot/drivers/phy/marvell/
H A Dcomphy_core.c110 int subnode; in comphy_probe() local
154 fdt_for_each_subnode(subnode, blob, node) { in comphy_probe()
156 if (!fdtdec_get_is_enabled(blob, subnode)) in comphy_probe()
160 blob, subnode, "phy-speed", PHY_TYPE_INVALID); in comphy_probe()
162 blob, subnode, "phy-type", PHY_SPEED_INVALID); in comphy_probe()
164 blob, subnode, "phy-invert", PHY_POLARITY_NO_INVERT); in comphy_probe()
165 comphy_map_data[lane].clk_src = fdtdec_get_bool(blob, subnode, in comphy_probe()
167 comphy_map_data[lane].end_point = fdtdec_get_bool(blob, subnode, in comphy_probe()
/OK3568_Linux_fs/u-boot/scripts/dtc/pylibfdt/
H A Dlibfdt.i_shipped134 """Get the offset of a named subnode
138 name: Name of the required subnode, e.g. 'subnode@1'
154 path: Path to the required node, e.g. '/node@3/subnode@1'
234 """Find the first subnode of a parent node
241 The offset of the first subnode, if any
244 FdtException if no subnode found or other error occurs
249 """Find the next subnode
252 nodeoffset: Node offset of previous subnode
256 The offset of the next subnode, if any
259 FdtException if no more subnode found or other error occurs
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/clock/
H A Dux500.txt13 - prcmu-clock: a subnode with one clock cell for PRCMU (power,
16 - prcc-periph-clock: a subnode with two clock cells for
22 - prcc-kernel-clock: a subnode with two clock cells for
28 - rtc32k-clock: a subnode with zero clock cells for the 32kHz
30 - smp-twd-clock: a subnode for the ARM SMP Timer Watchdog cluster
/OK3568_Linux_fs/u-boot/arch/arm/mach-tegra/
H A Dxusb-padctl-common.c223 ofnode subnode; in tegra_xusb_padctl_config_parse_dt() local
227 ofnode_for_each_subnode(subnode, node) { in tegra_xusb_padctl_config_parse_dt()
233 err = tegra_xusb_padctl_group_parse_dt(padctl, group, subnode); in tegra_xusb_padctl_config_parse_dt()
248 ofnode subnode; in tegra_xusb_padctl_parse_dt() local
257 ofnode_for_each_subnode(subnode, node) { in tegra_xusb_padctl_parse_dt()
260 debug("%s: subnode=%s\n", __func__, ofnode_get_name(subnode)); in tegra_xusb_padctl_parse_dt()
262 subnode); in tegra_xusb_padctl_parse_dt()
/OK3568_Linux_fs/u-boot/include/dm/
H A Dread.h87 * dev_read_subnode() - find a named subnode of a device
89 * @dev: device whose DT node contains the subnode
90 * @subnode_name: name of subnode to find
91 * @return reference to subnode (which can be invalid if there is no such
92 * subnode)
422 * dev_read_first_subnode() - find the first subnode of a device's node
425 * @return reference to the first subnode (which can be invalid if the device's
431 * ofnode_next_subnode() - find the next sibling of a subnode
434 * @return reference to the next subnode (which can be invalid if the node
713 * @subnode: ofnode holding the current subnode
[all …]

12345678910>>...14