Apollo Lake SoC GPIO Driver

OK thanks so now I have an UP2 Board and the driver is working.
Can you give me insight what pin is where on 40 pin header?

gpioc0=north bank
gpioc1=nortwest bank
gpioc2=west bank
gpioc3=southwest bank
 
I do notice that the caps<> field is empty for all gpiobus pins on UP2 and aplgpio.ko
I have seen boards with some empty caps but I assume they were system level peripherals like eMMC and display.

Code: 
# gpioctl -lv -f /dev/gpioc3
pin 00:    0    southwestbank0<IN>, caps:<>
pin 01:    0    southwestbank1<IN>, caps:<>
pin 02:    0    southwestbank2<IN>, caps:<>
pin 03:    0    southwestbank3<IN>, caps:<>
pin 04:    0    southwestbank4<IN>, caps:<>
pin 05:    0    southwestbank5<IN>, caps:<>
pin 06:    0    southwestbank6<IN>, caps:<>
pin 07:    0    southwestbank7<IN>, caps:<>

This doesn't help me here.
github.com

Pinout_UP2 · up-board/up-community Wiki

Contribute to up-board/up-community development by creating an account on GitHub.
github.com github.com
 
I have noticed that on Linux you have the four GPIO buses I quoted above.
But the they also have a fifth bus gpio4 which seems to be user pins: (See Comments)

How to get GPIO running using the new UP Squared Pro?

Hello, I followed the instructions from here but without any success to get the GPIO running with mraa under Ubuntu 18.04.5 (server) including the upboard-extras.
forum.up-community.org
The number of GPIO lines I get for aplgpio.ko is exactly the same as above post on Linux.
gpioc0=78 pins/lines
gpioc1=77
gpioc2=47
gpioc3=43
But no gpioc4 with aplgpio.ko ???
gpiochip4 [Raspberry Pi compatible UP GPIO] (28 lines)
Click to expand...
Is it possible the missing pins are not being properly exposed?
It seems really strange that all pins on gpio0,1,2,3 have empty caps.
I suspect they are hiding on the missing gpiochip4 bus. 28 Lines sounds right for the 40 pin GPIO header.
 
Last edited:
You must log in or register to reply here.
Back
Top