Changes between Version 27 and Version 28 of gpio

Timestamp:

12/15/2021 08:44:43 PM (3 years ago)

Author:

Tim Harvey

Comment:

updated U-Boot GPIO examples

gpio

@@ -656 +656 @@
 [=#uboot]
 = U-Boot GPIO
-The U-Boot bootloader has basic support for processor GPIO's.
+The U-Boot bootloader has basic support for GPIO's associated with a driver (such as processor GPIO's):
 
 Examples:
- * output logic high:
-{{{#!bash
-> gpio set 123
-}}}
- * output logic low:
-{{{#!bash
-> gpio clr 123
-}}}
- * show gpio's claimed by drivers:
-{{{#!bash
-> gpio status
-}}}
- * show gpio input:
-{{{#!bash
-> gpio input 123
+ * Show GPIO's
+{{{#!bash
+u-boot=> gpio status
+Bank GPIO1_:
+GPIO1_0: output: 0 [x] rs485_term.gpio-hog
+GPIO1_1: input: 0 [x] mipi_gpio4.gpio-hog
+GPIO1_6: output: 0 [x] pci_usb_sel.gpio-hog
+GPIO1_7: input: 1 [x] dio0.gpio-hog
+GPIO1_9: input: 1 [x] dio1.gpio-hog
+
+Bank GPIO2_:
+GPIO2_12: input: 1 [x] mmc@30b50000.cd-gpios
+
+Bank GPIO3_:
+GPIO3_0: output: 0 [x] ethernet@30be0000.phy-reset-gpios
+
+Bank GPIO4_:
+GPIO4_0: output: 0 [x] rs485_en.gpio-hog
+GPIO4_1: input: 0 [x] mipi_gpio3.gpio-hog
+GPIO4_2: output: 0 [x] rs485_hd.gpio-hog
+GPIO4_3: input: 0 [x] mipi_gpio2.gpio-hog
+GPIO4_4: input: 0 [x] mipi_gpio1.gpio-hog
+GPIO4_7: output: 1 [x] pci_wdis#.gpio-hog
+
+Bank GPIO5_:
+GPIO5_4: output: 0 [x] led-1.gpios
+GPIO5_5: output: 0 [x] led-0.gpios
+}}}
+ * show status of a particular GPIO (using the gpio id reported above)
+{{{#!bash
+u-boot=> gpio status GPIO4_7
+Bank GPIO4_:
+GPIO4_7: output: 1 [x] pci_wdis#.gpio-hog
+u-boot=> gpio status GPIO1_7
+Bank GPIO1_:
+GPIO1_7: input: 1 [x] dio0.gpio-hog
+u-boot=> 
+}}}
+  - above you can see that GPIO4_7 (the 'pci_wdis#' gpio on this board) is an output and currently driven high
+  - above you can see that GPIO1_7 (the 'dio0' gpio on this board) is an input and its current value is high
+  - note that a 0 always represents a voltage low and 1 always represents a voltage high regardless of if the gpio is considered 'active high' or 'active low' (which is typically indicated by the GPIO name as active low gpios typically end with a '#')
+ * set a gpio to output low (clr)
+{{{#!bash
+u-boot=> gpio clr GPIO4_7    
+gpio: pin GPIO4_7 (gpio 103) value is 0
+}}}
+ * set a gpio to output high (set)
+{{{#!bash
+u-boot=> gpio set GPIO4_7
+gpio: pin GPIO4_7 (gpio 103) value is 1
 }}}
  * toggle gpio:
 {{{#!bash
-> gpio toggle 123
-}}}
-
+u-boot=> gpio toggle GPIO4_7
+gpio: pin GPIO4_7 (gpio 103) value is 0
+u-boot=> gpio toggle GPIO4_7
+gpio: pin GPIO4_7 (gpio 103) value is 1
+}}}
+
+The value specified to the vaious gpio commands can be one of:
+ - bank name (ie GPIO4_ above) to represent all GPIO's in that bank
+ - pin name (ie GPIO4_7 above) to represent a specific gpio
+ - pin number (ie 103) to represent a specific gpio. The pin number notation is not recommended as it depends on GPIO controllers being registered in the same order which may not always be the case. It is always better to refer to the bank and pin name/notation.
+
+
+Note that on some platforms GPIO's can not be read back unless configured a specific way. This is the case on IMX boards where GPIO cells need to have the 'Software Input On' (SION) bit enabled in order to read it back. If you have such as GPIO you can still drive it high but you will get a wraning such as 'Warning: value of pin is still 0'. Additinally the 'toggle' won't function for these GPIO's as the software can't determine what state they are. 
 
 [=#notable_gpio]