1* Freescale IOMUX Controller (IOMUXC) for i.MX
2
3The IOMUX Controller (IOMUXC), together with the IOMUX, enables the IC
4to share one PAD to several functional blocks. The sharing is done by
5multiplexing the PAD input/output signals. For each PAD there are up to
68 muxing options (called ALT modes). Since different modules require
7different PAD settings (like pull up, keeper, etc) the IOMUXC controls
8also the PAD settings parameters.
9
10Please refer to pinctrl-bindings.txt in this directory for details of the
11common pinctrl bindings used by client devices, including the meaning of the
12phrase "pin configuration node".
13
14Freescale IMX pin configuration node is a node of a group of pins which can be
15used for a specific device or function. This node represents both mux and config
16of the pins in that group. The 'mux' selects the function mode(also named mux
17mode) this pin can work on and the 'config' configures various pad settings
18such as pull-up, open drain, drive strength, etc.
19
20Required properties for iomux controller:
21- compatible: "fsl,<soc>-iomuxc"
22  Please refer to each fsl,<soc>-pinctrl.txt binding doc for supported SoCs.
23
24Required properties for pin configuration node:
25- fsl,pins: two integers array, represents a group of pins mux and config
26  setting. The format is fsl,pins = <PIN_FUNC_ID CONFIG>, PIN_FUNC_ID is a
27  pin working on a specific function, which consists of a tuple of
28  <mux_reg conf_reg input_reg mux_val input_val>.  CONFIG is the pad setting
29  value like pull-up on this pin.
30
31Bits used for CONFIG:
32NO_PAD_CTL(1 << 31): indicate this pin does not need config.
33
34SION(1 << 30): Software Input On Field.
35Force the selected mux mode input path no matter of MUX_MODE functionality.
36By default the input path is determined by functionality of the selected
37mux mode (regular).
38
39Other bits are used for PAD setting.
40Please refer to each fsl,<soc>-pinctrl,txt binding doc for SoC specific part
41of bits definitions.
42
43NOTE:
44Some requirements for using fsl,imx-pinctrl binding:
451. We have pin function node defined under iomux controller node to represent
46   what pinmux functions this SoC supports.
472. The pin configuration node intends to work on a specific function should
48   to be defined under that specific function node.
49   The function node's name should represent well about what function
50   this group of pins in this pin configuration node are working on.
513. The driver can use the function node's name and pin configuration node's
52   name describe the pin function and group hierarchy.
53   For example, Linux IMX pinctrl driver takes the function node's name
54   as the function name and pin configuration node's name as group name to
55   create the map table.
564. Each pin configuration node should have a phandle, devices can set pins
57   configurations by referring to the phandle of that pin configuration node.
58
59Examples:
60usdhc@0219c000 { /* uSDHC4 */
61	fsl,card-wired;
62	vmmc-supply = <&reg_3p3v>;
63	status = "okay";
64	pinctrl-names = "default";
65	pinctrl-0 = <&pinctrl_usdhc4_1>;
66};
67
68iomuxc@020e0000 {
69	compatible = "fsl,imx6q-iomuxc";
70	reg = <0x020e0000 0x4000>;
71
72	/* shared pinctrl settings */
73	usdhc4 {
74		pinctrl_usdhc4_1: usdhc4grp-1 {
75			fsl,pins = <1386 0x17059	/* MX6Q_PAD_SD4_CMD__USDHC4_CMD */
76				    1392 0x10059	/* MX6Q_PAD_SD4_CLK__USDHC4_CLK	*/
77				    1462 0x17059	/* MX6Q_PAD_SD4_DAT0__USDHC4_DAT0 */
78				    1470 0x17059	/* MX6Q_PAD_SD4_DAT1__USDHC4_DAT1 */
79				    1478 0x17059	/* MX6Q_PAD_SD4_DAT2__USDHC4_DAT2 */
80				    1486 0x17059	/* MX6Q_PAD_SD4_DAT3__USDHC4_DAT3 */
81				    1493 0x17059	/* MX6Q_PAD_SD4_DAT4__USDHC4_DAT4 */
82				    1501 0x17059	/* MX6Q_PAD_SD4_DAT5__USDHC4_DAT5 */
83				    1509 0x17059	/* MX6Q_PAD_SD4_DAT6__USDHC4_DAT6 */
84				    1517 0x17059>;	/* MX6Q_PAD_SD4_DAT7__USDHC4_DAT7 */
85		};
86	};
87	....
88};
89Refer to the IOMUXC controller chapter in imx6q datasheet,
900x17059 means enable hysteresis, 47KOhm Pull Up, 50Mhz speed,
9180Ohm driver strength and Fast Slew Rate.
92User should refer to each SoC spec to set the correct value.
93
94TODO: when dtc macro support is available, we can change above raw data
95to dt macro which can get better readability in dts file.
96