aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/dts/3G150B.dts
diff options
context:
space:
mode:
authorMathias Kresin <dev@kresin.me>2018-08-22 06:26:36 +0200
committerMathias Kresin <dev@kresin.me>2018-08-23 22:40:59 +0200
commit28de86e8169597a70905211e41c8e9b38aab97f0 (patch)
tree5c2548b80ed86eaf535f6f7df81b98e7fe3616ee /target/linux/ramips/dts/3G150B.dts
parent6b13238a132c6c6e7a12b708e2655002e94c12a8 (diff)
downloadupstream-28de86e8169597a70905211e41c8e9b38aab97f0.tar.gz
upstream-28de86e8169597a70905211e41c8e9b38aab97f0.tar.bz2
upstream-28de86e8169597a70905211e41c8e9b38aab97f0.zip
ramips: drop not existing groups from pinmux
RT5350 neither have rgmii nor a mdio pinmux group. MT7628an doesn't have a jtag group. Having these groups defined might cause a boot panic. The pin controller fails to initialise for kernels > 4.9 if invalid groups are used. If a subsystem references a pin controller configuration node, it can not find this node and errors out. In worst case it's the SPI driver which errors out and we have no root filesystem to mount. Signed-off-by: Mathias Kresin <dev@kresin.me>
Diffstat (limited to 'target/linux/ramips/dts/3G150B.dts')
-rw-r--r--target/linux/ramips/dts/3G150B.dts2
1 files changed, 1 insertions, 1 deletions
diff --git a/target/linux/ramips/dts/3G150B.dts b/target/linux/ramips/dts/3G150B.dts
index 601d6c6b32..90a52fa8bc 100644
--- a/target/linux/ramips/dts/3G150B.dts
+++ b/target/linux/ramips/dts/3G150B.dts
@@ -96,7 +96,7 @@
&pinctrl {
state_default: pinctrl0 {
gpio {
- ralink,group = "i2c", "jtag", "rgmii", "mdio", "uartf", "led";
+ ralink,group = "i2c", "jtag", "uartf", "led";
ralink,function = "gpio";
};
};