aboutsummaryrefslogtreecommitdiffstats
path: root/arch/powerpc/boot/dts/fsl/t2081si-post.dtsi
diff options
context:
space:
mode:
authorGregory CLEMENT <gregory.clement@free-electrons.com>2014-12-17 18:07:23 +0100
committerAndrew Lunn <andrew@lunn.ch>2014-12-21 06:01:05 -0600
commitd4b0833a65e8b9fc58d992ba0cc89cad1580db31 (patch)
treeaa3065248a90322650d2f01b32a132e30fcb5888 /arch/powerpc/boot/dts/fsl/t2081si-post.dtsi
parentLinux 3.19-rc1 (diff)
downloadlinux-dev-d4b0833a65e8b9fc58d992ba0cc89cad1580db31.tar.xz
linux-dev-d4b0833a65e8b9fc58d992ba0cc89cad1580db31.zip
ARM: mvebu: Fix pinctrl configuration for Armada 370 DB
The commit b4607572ef86 (ARM: mvebu: remove conflicting muxing on Armada 370 DB) removes the hog pins muxing. As it is explained in the commit log it solves a warning a boot time, but more important it also allows using the Giga port 0 of the board. Unfortunately in the same time the commit 4904a82a9399 (arm: mvebu: move Armada 370/XP pinctrl node definition armada-370-xp.dtsi) was merged and it introduced again the hog pins muxing. Because of it, the Giga port 0 of the board is no more usable. This commit remove again the conflicting muxing (hopefully for the last time). Signed-off-by: Gregory CLEMENT <gregory.clement@free-electrons.com> [andrew@lunn.ch: Correct commit IDs] Signed-off-by: Andrew Lunn <andrew@lunn.ch> Fixes: 4904a82a9399 ("arm: mvebu: move Armada 370/XP pinctrl node definition armada-370-xp.dtsi")
Diffstat (limited to 'arch/powerpc/boot/dts/fsl/t2081si-post.dtsi')
0 files changed, 0 insertions, 0 deletions