mirror of
https://github.com/hardkernel/linux.git
synced 2026-03-25 20:10:23 +09:00
3b7424f332
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>