1 * Renesas Pin Function Controller (GPIO and Pin Mux/Config)
3 The Pin Function Controller (PFC) is a Pin Mux/Config controller. On SH7372,
4 SH73A0, R8A73A4 and R8A7740 it also acts as a GPIO controller.
12 - compatible: should be one of the following.
13 - "renesas,pfc-r8a73a4": for R8A73A4 (R-Mobile APE6) compatible pin-controller.
14 - "renesas,pfc-r8a7740": for R8A7740 (R-Mobile A1) compatible pin-controller.
15 - "renesas,pfc-r8a7778": for R8A7778 (R-Mobile M1) compatible pin-controller.
16 - "renesas,pfc-r8a7779": for R8A7779 (R-Car H1) compatible pin-controller.
17 - "renesas,pfc-r8a7790": for R8A7790 (R-Car H2) compatible pin-controller.
18 - "renesas,pfc-r8a7791": for R8A7791 (R-Car M2) compatible pin-controller.
19 - "renesas,pfc-sh7372": for SH7372 (SH-Mobile AP4) compatible pin-controller.
20 - "renesas,pfc-sh73a0": for SH73A0 (SH-Mobile AG5) compatible pin-controller.
22 - reg: Base address and length of each memory resource used by the pin
23 controller hardware module.
27 - #gpio-range-cells: Mandatory when the PFC doesn't handle GPIO, forbidden
28 otherwise. Should be 3.
30 - interrupts-extended: Specify the interrupts associated with external
31 IRQ pins. This property is mandatory when the PFC handles GPIOs and
32 forbidden otherwise. When specified, it must contain one interrupt per
33 external IRQ, sorted by external IRQ number.
35 The PFC node also acts as a container for pin configuration nodes. Please refer
36 to pinctrl-bindings.txt in this directory for the definition of the term "pin
37 configuration node" and for the common pinctrl bindings used by client devices.
39 Each pin configuration node represents a desired configuration for a pin, a
40 pin group, or a list of pins or pin groups. The configuration can include the
41 function to select on those pin(s) and pin configuration parameters (such as
42 pull-up and pull-down).
44 Pin configuration nodes contain pin configuration properties, either directly
45 or grouped in child subnodes. Both pin muxing and configuration parameters can
46 be grouped in that way and referenced as a single pin configuration node by
49 A configuration node or subnode must reference at least one pin (through the
50 pins or pin groups properties) and contain at least a function or one
51 configuration parameter. When the function is present only pin groups can be
52 used to reference pins.
54 All pin configuration nodes and subnodes names are ignored. All of those nodes
55 are parsed through phandles and processed purely based on their content.
57 Pin Configuration Node Properties:
59 - renesas,pins : An array of strings, each string containing the name of a pin.
60 - renesas,groups : An array of strings, each string containing the name of a pin
63 - renesas,function: A string containing the name of the function to mux to the
64 pin group(s) specified by the renesas,groups property
66 Valid values for pin, group and function names can be found in the group and
67 function arrays of the PFC data file corresponding to the SoC
68 (drivers/pinctrl/sh-pfc/pfc-*.c)
70 The pin configuration parameters use the generic pinconf bindings defined in
71 pinctrl-bindings.txt in this directory. The supported parameters are
72 bias-disable, bias-pull-up and bias-pull-down.
78 On SH7372, SH73A0, R8A73A4 and R8A7740 the PFC node is also a GPIO controller
83 - gpio-controller: Marks the device node as a gpio controller.
85 - #gpio-cells: Should be 2. The first cell is the GPIO number and the second
86 cell specifies GPIO flags, as defined in <dt-bindings/gpio/gpio.h>. Only the
87 GPIO_ACTIVE_HIGH and GPIO_ACTIVE_LOW flags are supported.
89 The syntax of the gpio specifier used by client nodes should be the following
90 with values derived from the SoC user manual.
92 <[phandle of the gpio controller node]
93 [pin number within the gpio controller]
96 On other mach-shmobile platforms GPIO is handled by the gpio-rcar driver.
97 Please refer to Documentation/devicetree/bindings/gpio/renesas,gpio-rcar.txt
98 for documentation of the GPIO device tree bindings on those platforms.
104 Example 1: SH73A0 (SH-Mobile AG5) pin controller node
107 compatible = "renesas,pfc-sh73a0";
108 reg = <0xe6050000 0x8000>,
112 interrupts-extended =
113 <&irqpin0 0 0>, <&irqpin0 1 0>, <&irqpin0 2 0>, <&irqpin0 3 0>,
114 <&irqpin0 4 0>, <&irqpin0 5 0>, <&irqpin0 6 0>, <&irqpin0 7 0>,
115 <&irqpin1 0 0>, <&irqpin1 1 0>, <&irqpin1 2 0>, <&irqpin1 3 0>,
116 <&irqpin1 4 0>, <&irqpin1 5 0>, <&irqpin1 6 0>, <&irqpin1 7 0>,
117 <&irqpin2 0 0>, <&irqpin2 1 0>, <&irqpin2 2 0>, <&irqpin2 3 0>,
118 <&irqpin2 4 0>, <&irqpin2 5 0>, <&irqpin2 6 0>, <&irqpin2 7 0>,
119 <&irqpin3 0 0>, <&irqpin3 1 0>, <&irqpin3 2 0>, <&irqpin3 3 0>,
120 <&irqpin3 4 0>, <&irqpin3 5 0>, <&irqpin3 6 0>, <&irqpin3 7 0>;
123 Example 2: A GPIO LED node that references a GPIO
125 #include <dt-bindings/gpio/gpio.h>
128 compatible = "gpio-leds";
130 gpios = <&pfc 20 GPIO_ACTIVE_LOW>;
134 Example 3: KZM-A9-GT (SH-Mobile AG5) default pin state hog and pin control maps
135 for the MMCIF and SCIFA4 devices
138 pinctrl-0 = <&scifa4_pins>;
139 pinctrl-names = "default";
143 renesas,groups = "mmc0_data8_0", "mmc0_ctrl_0";
144 renesas,function = "mmc0";
147 renesas,groups = "mmc0_data8_0";
148 renesas,pins = "PORT279";
153 scifa4_pins: scifa4 {
154 renesas,groups = "scifa4_data", "scifa4_ctrl";
155 renesas,function = "scifa4";
159 Example 4: KZM-A9-GT (SH-Mobile AG5) default pin state for the MMCIF device
162 pinctrl-0 = <&mmcif_pins>;
163 pinctrl-names = "default";
166 vmmc-supply = <®_1p8v>;