ramips: drop not existing groups from pinmux
authorMathias Kresin <dev@kresin.me>
Wed, 22 Aug 2018 04:26:36 +0000 (06:26 +0200)
committerMathias Kresin <dev@kresin.me>
Thu, 23 Aug 2018 20:40:59 +0000 (22:40 +0200)
commit28de86e8169597a70905211e41c8e9b38aab97f0
tree5c2548b80ed86eaf535f6f7df81b98e7fe3616ee
parent6b13238a132c6c6e7a12b708e2655002e94c12a8
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>
target/linux/ramips/dts/3G150B.dts
target/linux/ramips/dts/ALL5003.dts
target/linux/ramips/dts/DIR-300-B7.dts
target/linux/ramips/dts/DIR-320-B1.dts
target/linux/ramips/dts/MPRA1.dts
target/linux/ramips/dts/MPRA2.dts
target/linux/ramips/dts/NCS601W.dts
target/linux/ramips/dts/RT5350F-OLINUXINO.dtsi
target/linux/ramips/dts/WIZARD8800.dts
target/linux/ramips/dts/WRTNODE2P.dts