xref: /freebsd/sys/contrib/device-tree/Bindings/pinctrl/qcom,msm8660-pinctrl.txt (revision 59c8e88e72633afbc47a4ace0d2170d00d51f7dc) 
1Qualcomm MSM8660 TLMM block
2
3Required properties:
4- compatible: "qcom,msm8660-pinctrl"
5- reg: Should be the base address and length of the TLMM block.
6- interrupts: Should be the parent IRQ of the TLMM block.
7- interrupt-controller: Marks the device node as an interrupt controller.
8- #interrupt-cells: Should be two.
9- gpio-controller: Marks the device node as a GPIO controller.
10- #gpio-cells : Should be two.
11                The first cell is the gpio pin number and the
12                second cell is used for optional parameters.
13- gpio-ranges: see ../gpio/gpio.txt
14
15Optional properties:
16
17- gpio-reserved-ranges: see ../gpio/gpio.txt
18
19Please refer to ../gpio/gpio.txt and ../interrupt-controller/interrupts.txt for
20a general description of GPIO and interrupt bindings.
21
22Please refer to pinctrl-bindings.txt in this directory for details of the
23common pinctrl bindings used by client devices, including the meaning of the
24phrase "pin configuration node".
25
26Qualcomm's pin configuration nodes act as a container for an arbitrary number of
27subnodes. Each of these subnodes represents some desired configuration for a
28pin, a group, or a list of pins or groups. This configuration can include the
29mux function to select on those pin(s)/group(s), and various pin configuration
30parameters, such as pull-up, drive strength, etc.
31
32The name of each subnode is not important; all subnodes should be enumerated
33and processed purely based on their content.
34
35Each subnode only affects those parameters that are explicitly listed. In
36other words, a subnode that lists a mux function but no pin configuration
37parameters implies no information about any pin configuration parameters.
38Similarly, a pin subnode that describes a pullup parameter implies no
39information about e.g. the mux function.
40
41
42The following generic properties as defined in pinctrl-bindings.txt are valid
43to specify in a pin configuration subnode:
44
45 pins, function, bias-disable, bias-pull-down, bias-pull-up, drive-strength,
46 output-low, output-high.
47
48Non-empty subnodes must specify the 'pins' property.
49
50Valid values for pins are:
51  gpio0-gpio172, sdc3_clk, sdc3_cmd, sdc3_data sdc4_clk, sdc4_cmd, sdc4_data
52
53Valid values for function are:
54  gpio, cam_mclk, dsub, ext_gps, gp_clk_0a, gp_clk_0b, gp_clk_1a, gp_clk_1b,
55  gp_clk_2a, gp_clk_2b, gp_mn, gsbi1, gsbi1_spi_cs1_n, gsbi1_spi_cs2a_n,
56  gsbi1_spi_cs2b_n, gsbi1_spi_cs3_n, gsbi2, gsbi2_spi_cs1_n, gsbi2_spi_cs2_n,
57  gsbi2_spi_cs3_n, gsbi3, gsbi3_spi_cs1_n, gsbi3_spi_cs2_n, gsbi3_spi_cs3_n,
58  gsbi4, gsbi5, gsbi6, gsbi7, gsbi8, gsbi9, gsbi10, gsbi11, gsbi12, hdmi, i2s,
59  lcdc, mdp_vsync, mi2s, pcm, ps_hold, sdc1, sdc2, sdc5, tsif1, tsif2, usb_fs1,
60  usb_fs1_oe_n, usb_fs2, usb_fs2_oe_n, vfe, vsens_alarm, ebi2, ebi2cs
61
62Example:
63
64	msmgpio: pinctrl@800000 {
65		compatible = "qcom,msm8660-pinctrl";
66		reg = <0x800000 0x4000>;
67
68		gpio-controller;
69		#gpio-cells = <2>;
70		gpio-ranges = <&msmgpio 0 0 173>;
71		interrupt-controller;
72		#interrupt-cells = <2>;
73		interrupts = <0 16 0x4>;
74
75		pinctrl-names = "default";
76		pinctrl-0 = <&gsbi12_uart>;
77
78		gsbi12_uart: gsbi12-uart {
79			mux {
80				pins = "gpio117", "gpio118";
81				function = "gsbi12";
82			};
83
84			tx {
85				pins = "gpio118";
86				drive-strength = <8>;
87				bias-disable;
88			};
89
90			rx {
91				pins = "gpio117";
92				drive-strength = <2>;
93				bias-pull-up;
94			};
95		};
96	};
97