aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/omap/base-files/etc
diff options
context:
space:
mode:
authorJohn Crispin <john@openwrt.org>2016-02-26 08:35:35 +0000
committerJohn Crispin <john@openwrt.org>2016-02-26 08:35:35 +0000
commitf998540e80baa20f5248f94bb78f414bd3eaedc1 (patch)
treee14dc4bb89cbd872f046b78c754213bfac9668db /target/linux/omap/base-files/etc
parent82a8f5fdaab4a3290d9a9d3c9f5dce0db598e63e (diff)
downloadupstream-f998540e80baa20f5248f94bb78f414bd3eaedc1.tar.gz
upstream-f998540e80baa20f5248f94bb78f414bd3eaedc1.tar.bz2
upstream-f998540e80baa20f5248f94bb78f414bd3eaedc1.zip
ramips: fix GPIO names for RT5350F-OLinuXino-EVB
Hi, the board in subject (RT5350F-OLinuXino-EVB) still ships from vendor with a RC3 image built upon a .dts file which declares GPIO12 and GPIO14 as relay2 and relay1 respectively, as you can see from their rt5350f branch on GitHub. For some reason in the official stable build both the GPIOs are swapped and the wrong names are declared in the gpio-export directive. I'm submitting this patch which should roll back the wrong changes, so that we get backward compatibility with any script developed on RC3 which controls the relays. After patching correct operation is restored: root@OpenWrt:/# cat /sys/kernel/debug/gpio GPIOs 0-21, platform/10000600.gpio, 10000600.gpio: gpio-0 (button ) in hi gpio-12 (relay2 ) out lo gpio-14 (relay1 ) out lo Thank you, Signed-off-by: Lorenzo Cafaro <lorenzo@ibisco.net> SVN-Revision: 48796
Diffstat (limited to 'target/linux/omap/base-files/etc')
0 files changed, 0 insertions, 0 deletions