How to identify GPIO pins

vbguy2011 · July 5, 2018, 1:45pm

I’m trying to update R64.GPIO for rock960, but I am having a hard time trying to figure out what the header pins are for GPIO.

I only managed to figure out the following pins so far:
Rock960 Signals - GPIO pin
GPIO0_A2 - 1002
GPIO0_A6 - 1006
GPIO1_B1 - 1041
GPIO1_B2 - 1042
GPIO1_C2 - 1050
GPIO1_C7 - 1055
GPIO3_D1 - 1121
GPIO3_D4 - 1124
GPIO3_D5 - 1125
GPIO4_A0 - 1128
GPIO4_A3 - 1131
GPIO4_A4 - 1132

Is there any documentation that would assist?

edit: ok, I’ve just done some simple calculation and deduction to come up with the pins myself…

Loic · July 5, 2018, 1:29pm

The rock960 <-> 96boards LS matching is available at:

I don’t find any document related to gpio-linux <-> gpio-soc matching, however we can find it relatively easily.

If you look in /sys/class/gpio you will see 5 gpio chips registered.

root@rock960:/sys/class/gpio# ls
export        gpiochip1032  gpiochip1096  unexport
gpiochip1000  gpiochip1064  gpiochip1128

We can assume that the GPIO chips correspond to SoC GPIO controller 0,1, 2, 3, 4.
GPIO0_X is exposed as gpiochip1000, GPIO1 as gpiochip1032, etc… each one seems to register 32 GPIOs.
These 32 gpios seem split in four groups of 8 gpios (A, B, C, D), A0 being at offset 0, B0 at offset 8, etc…
So if I’m not wrong : gpio = (1000 + 32 * controller_idx) + gpio_offset

GPIO0_A6 = 1006
GPIO0_A2 = 1002
GPIO1_B1 = 1041
…

Would be nice to have this added to the documentation and to libmraa.

vbguy2011 · July 5, 2018, 1:47pm

Thanks! I figured it the same way, and already tested to be sure.

Also, how is rock960 <-> 96boards LS matching any useful generally?

edit: I’ll upload the modded R64.GPIO python GPIO library (original at https://github.com/Leapo/Rock64-R64.GPIO) in a little while. It’s pretty useful given the amount of resources using RPi.GPIO

Loic · July 5, 2018, 2:32pm

I don’t really understand is the reason why GPIO numbers start at offset 1000… nothing in the upstream driver indicates this. Nevermind…

Now you have the full matching: Linux <-> SoC <-> LS.

hipboi · July 9, 2018, 7:01am

Here is some explaination about gpio offset starting from 1000:

github.com/rockchip-linux/kernel

pinctrl: rockchip: Make the gpio base started from 1000

committed 10:16AM - 05 Sep 17 UTC

SuperDavidWu

+6 -4

If the gpio base is started from 1000, the "gpio = 0" will be invalid, that can… avoid something unforeseen. The real pin number is "gpio number - 1000". If you cat the gpio log, you will see the log like this: rk3399:/ # cat d/gpio GPIOs 1000-1031, platform/pinctrl, gpio0: gpio-1004 ( |bt_default_wake_host) in lo gpio-1005 ( |power ) in hi gpio-1009 ( |bt_default_reset ) out lo gpio-1010 ( |reset ) out lo gpio-1011 ( |? ) out hi GPIOs 1032-1063, platform/pinctrl, gpio1: gpio-1034 ( |int-n ) in hi gpio-1035 ( |vbus-5v ) out lo gpio-1036 ( |vbus-5v ) out lo gpio-1045 ( |enable ) out hi gpio-1046 ( |vsel ) out lo gpio-1049 ( |vsel ) out lo gpio-1056 ( |int-n ) in hi GPIOs 1064-1095, platform/pinctrl, gpio2: gpio-1083 ( |bt_default_rts ) in hi gpio-1090 ( |bt_default_wake ) in hi GPIOs 1096-1127, platform/pinctrl, gpio3: gpio-1111 ( |mdio-reset ) out hi GPIOs 1128-1159, platform/pinctrl, gpio4: gpio-1150 ( |? ) out hi gpio-1153 ( |vcc5v0_host ) out hi gpio-1156 ( |hp det ) in hi Change-Id: I744ddc1df6075b0a044d65c65622e2a59f3a332e Signed-off-by: David Wu <david.wu@rock-chips.com>

dbqpdb · October 30, 2018, 11:36pm

vbguy2011, did you ever get a modded R64.gpio package working? I’d love to get my hands on it.