Changes between Version 7 and Version 8 of gpio

Timestamp:

09/27/2018 11:21:29 PM (6 years ago)

Author:

Tim Harvey

Comment:

added Newport GPIO information

gpio

@@ -96 +96 @@
 The various product hardware manuals will call out GPIO devices on the board and provide a table mapping the GPIO to a GPIO host controller, a function, and a connector pinout (if going off-board).
 
-This hardware mapping is defined in the Linux kernel device-tree for Ventana (ie [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/imx6qdl-gw54xx.dtsi arch/arm/boot/dts/imx6qdl-gw54xx.dtsi]) or in the kernel board-support file for other product families (file, ie [https://dev.openwrt.org/browser/trunk/target/linux/cns3xxx/files/arch/arm/mach-cns3xxx/laguna.c arch/arm/mach-cns3xxx/laguna.c]).
-
-If debugfs is enabled in the kernel (as it is on Gateworks BSP's) you can see a nice table of GPIO mapping via {{{/sys/kernel/debug/gpio}}}. Some examples:
- * GW5400:
+This hardware mapping is defined in the following files depending on board/family:
+* Ventana: Linux kernel device-tree (ie [http://github.com/Gateworks/dts-newport])
+* Ventana: Linux kernel device-tree (ie [http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/imx6qdl-gw54xx.dtsi arch/arm/boot/dts/imx6qdl-gw54xx.dtsi])
+* Laguna: Linux kernel board-support files (ie [https://github.com/Gateworks/openwrt/blob/16.02/target/linux/cns3xxx/files/arch/arm/mach-cns3xxx/laguna.c arch/arm/mach-cns3xxx/laguna.c]).
+
+If debugfs is enabled in the kernel and mounted (as it is on Gateworks BSP's) you can see a nice table of GPIO mapping via {{{/sys/kernel/debug/gpio}}}. Some examples:
+ * Newport GW6400:
+{{{#!bash
+# cat /sys/kernel/debug/gpio 
+gpiochip1: GPIOs 448-463, parent: i2c/0-0023, pca9555, can sleep:
+
+gpiochip0: GPIOs 464-511, parent: pci/0000:00:06.0, gpio_thunderx:
+ gpio-472 (                    |mmc_supply_3v3      ) out hi    
+ gpio-478 (                    |user2               ) out lo    
+ gpio-495 (                    |user1               ) out lo   
+}}}
+ * Ventana GW5400:
 {{{#!bash
 # cat /sys/kernel/debug/gpio 
@@ -128 +141 @@
 }}}
   * Note that this does not show GPIO's that are not used by Linux drivers such as USB HUB reset, Ethernet PHY reset, etc.
- * GW2388:
+ * Laguna GW2388:
 {{{#!bash
 # cat /sys/kernel/debug/gpio 
@@ -146 +159 @@
  gpio-115 (user1               ) out hi
 }}}
- * GW2387:
+ * Laguna GW2387:
 {{{#!bash
 # cat /sys/kernel/debug/gpio 
@@ -167 +180 @@
 
 Product Family specific notes:
+ * Newport:
+  - CN80XX GPIOs: The CN80XX has one 48bit GPIO controller
+   - GPIO![0-48]: gpio-464 to gpio-511
  * Ventana:
   - IMX6 GPIOs: The IMX6 has 7 32bit GPIO controllers for a possible 224 fast ARM based GPIO's
@@ -189 +205 @@
   - additional i2c based GPIO port-expanders present on some boards would begin at gpio116
 
+Note that the Linux gpio mapping is not guaranteed to remain constant across kernel versions. Care should be taken to consult {{{/sys/kernel/debug/gpio}}} and {{{/sys/class/gpio}}} when changing kernel versions.
 
 When referring to [http://www.gateworks.com/usermanuals Gateworks board user hardware manuals] you will need to translate the hardware pin name to a gpio using the information above. Some examples:
+ * Newport GPIO8 would be the 8th IO on the CN80XX GPIO controller thus map to gpio-472.
  * Laguna GPIOA8 would be the 9th IO on the GPIOA controller (the first is GPIOA0) thus map to gpio 0+8 = gpio-8
  * Laguna GPIOB1 would be the 2nd IO on the GPIOB controller thus map to gpio 32+2 = gpio-34
@@ -448 +466 @@
  * [wiki:OpenWrt/gpio GPIO in OpenWrt]
  * [wiki:ventana/DigitalIO Ventana product family Digital I/O]
+ * [wiki:newport/DigitalIO Newport product family Digital I/O]