bindings/pinctrl/pinctrl-bindings.txt

4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
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
25 For example, a pin controller may set up its own "active" state when the
35 For each client device individually, every pin state is assigned an integer
36 ID. These numbers start at 0, and are contiguous. For each state ID, a unique
37 property exists to define the pin configuration. Each state may also be
42 defined in its device tree node, and whether to define the set of state
43 IDs that must be provided, or whether to define the set of state names that
47 pinctrl-0:	List of phandles, each pointing at a pin configuration
51 		controllers may be configured, or so that a state may be built
57 		In some cases, it may be useful to define a state, but for it
65 pinctrl-1:	List of phandles, each pointing at a pin configuration
68 pinctrl-n:	List of phandles, each pointing at a pin configuration
70 pinctrl-names:	The list of names to assign states. List entry 0 defines the
71 		name for integer state ID 0, list entry 1 for state ID 1, and
78 		pinctrl-names = "active", "idle";
79 		pinctrl-0 = <&state_0_node_a>;
80 		pinctrl-1 = <&state_1_node_a>, <&state_1_node_b>;
83 	/* For the same device if using state IDs */
85 		pinctrl-0 = <&state_0_node_a>;
86 		pinctrl-1 = <&state_1_node_a>, <&state_1_node_b>;
94 		pinctrl-names = "active", "idle";
95 		pinctrl-0 = <>;
96 		pinctrl-1 = <>;
105 See pinmux-node.yaml
109 See pincfg-node.yaml