Lines Matching +full:pin +full:-

3 Hardware modules that control pin multiplexing or configuration parameters
4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
5 controllers. Each pin controller must be represented as a node in device tree,
8 Hardware modules whose signals are affected by pin configuration are
12 For a client device to operate correctly, certain pin controllers must
13 set up certain specific pin configurations. Some client devices need a
14 single static pin configuration, e.g. set up during initialization. Others
15 need to reconfigure pins at run-time, for example to tri-state pins when the
21 for client device device tree nodes to map those state names to the pin
24 Note that pin controllers themselves may also be client devices of themselves.
25 For example, a pin controller may set up its own "active" state when the
26 driver loads. This would allow representing a board's static pin configuration
31 they require certain specific named states for dynamic pin configuration.
35 For each client device individually, every pin state is assigned an integer
37 property exists to define the pin configuration. Each state may also be
47 pinctrl-0:	List of phandles, each pointing at a pin configuration
48 		node. These referenced pin configuration nodes must be child
49 		nodes of the pin controller that they configure. Multiple
50 		entries may exist in this list so that multiple pin
52 		from multiple nodes for a single pin controller, each
55 		pin configuration nodes.
59 		used in an SoC either without a pin controller, or where the
60 		pin controller does not affect the HW module in question. If
61 		the binding for that IP block requires certain pin states to
65 pinctrl-1:	List of phandles, each pointing at a pin configuration
66 		node within a pin controller.
68 pinctrl-n:	List of phandles, each pointing at a pin configuration
69 		node within a pin controller.
70 pinctrl-names:	The list of names to assign states. List entry 0 defines the
78 		pinctrl-names = "active", "idle";
79 		pinctrl-0 = <&state_0_node_a>;
80 		pinctrl-1 = <&state_1_node_a>, <&state_1_node_b>;
85 		pinctrl-0 = <&state_0_node_a>;
86 		pinctrl-1 = <&state_1_node_a>, <&state_1_node_b>;
90 	 * For an IP block whose binding supports pin configuration,
91 	 * but in use on an SoC that doesn't have any pin control hardware
94 		pinctrl-names = "active", "idle";
95 		pinctrl-0 = <>;
96 		pinctrl-1 = <>;
99 == Pin controller devices ==
103 == Generic pin multiplexing node content ==
105 See pinmux-node.yaml
107 == Generic pin configuration node content ==
109 See pincfg-node.yaml