summaryrefslogtreecommitdiff
path: root/target/linux/ramips/dts/mt7620n.dtsi
diff options
context:
space:
mode:
authorJohn Crispin <john@openwrt.org>2015-10-05 10:26:40 +0000
committerJohn Crispin <john@openwrt.org>2015-10-05 10:26:40 +0000
commitd4cd8f89eb044d1e2bf6a7962a3a5ca970e4dcf9 (patch)
tree19f3055cf6ab1225f7b3e9603187ee383bbdc488 /target/linux/ramips/dts/mt7620n.dtsi
parentaecac14cc42d2759822cb8da477ef18288342e87 (diff)
downloadmtk-20170518-d4cd8f89eb044d1e2bf6a7962a3a5ca970e4dcf9.zip
mtk-20170518-d4cd8f89eb044d1e2bf6a7962a3a5ca970e4dcf9.tar.gz
mtk-20170518-d4cd8f89eb044d1e2bf6a7962a3a5ca970e4dcf9.tar.bz2
ramips: Ralink RT3883 RGMII pinmux fix.
Due to datasheet of rt3883 SoC rgmii1 port handles pins 84-95 and rgmii2 port handles pins 72-83. When this function ports gets added to rt3883_pinmux_data there's wrong pinmux bits set (RT3883_GPIO_MODE_GE1 manages 84-95 pins and RT3883_GPIO_MODE_GE2 manages 72-83). So when enabling rgmii2 as GPIO driver confuses hardware and nothing work, neither rgmii nor gpio. Also in '0030-pinctrl-ralink-add-pinctrl-driver.patch' typo in name of rgmii2 port. Signed-off-by: Nick Leiten <nickleiten@gmail.com> SVN-Revision: 47118
Diffstat (limited to 'target/linux/ramips/dts/mt7620n.dtsi')
0 files changed, 0 insertions, 0 deletions