...

• Helpful Debug Messages: Sometimes it is helpful to see how the pins are being configured on boot up. By putting #define DEBUG at the top of the driver file (pinctrl.c or pinctrl-rzg2.c) will make it print out how each pins is being configured.

Device Tree Examples

• (see device tree for evaluation board)
• Use any GPIO as wake-up source, e.g. P37.2:

• Expand
  title Use any GPIO as wake-up source, e.g. P37.2:
  gpio_keys { compatible = "gpio-keys"; #address-cells = <1>; #size-cells = <0>; autorepeat; P37_2 { label = "GPIO Key WAKEUP"; linux,code = <143>; wakeup-source; interrupt-parent = <&pinctrl>; interrupts = <RZG2L_GPIO(37, 2) IRQ_TYPE_EDGE_FALLING>; debounce-interval = <50>; }; };

• Expand
  title Example of defining a GPIO with pull-down
  test-gpio { gpio-hog; gpios = <RZG2L_GPIO(6, 0) (GPIO_ACTIVE_HIGH | GPIO_PULL_DOWN)>; input; line-name = "test_gpio"; };

IRQ0-7

Linux Drivers

• RZ/G2H, G2M, G2N, G2E:
  • CONFIG_xxx=y

...

PMIC RAA215300

Linux Drivers

• • drivers/mfd/raa215300.c
  • CONFIG_PMIC_RAA215300=y
  • Documentation/devicetree/bindings/mfd/raa215300.txt

Notes

• Only supports RTC function
• Added in VLP/G v3.0.1 release (branch rz-5.10-cip13)

...