diff options
Diffstat (limited to 'target/linux/mvebu/patches-3.8/011-arm_mvebu_add_pin_mux_options_a370.patch')
-rw-r--r-- | target/linux/mvebu/patches-3.8/011-arm_mvebu_add_pin_mux_options_a370.patch | 34 |
1 files changed, 0 insertions, 34 deletions
diff --git a/target/linux/mvebu/patches-3.8/011-arm_mvebu_add_pin_mux_options_a370.patch b/target/linux/mvebu/patches-3.8/011-arm_mvebu_add_pin_mux_options_a370.patch deleted file mode 100644 index 4072ae50cd..0000000000 --- a/target/linux/mvebu/patches-3.8/011-arm_mvebu_add_pin_mux_options_a370.patch +++ /dev/null @@ -1,34 +0,0 @@ -The SDIO interface is available either on pins MPP9/11/12/13/14/15 or -MPP47/48/49/50/51/52 on the Armada 370. Even though all combinations -are potentially possible, those two muxing options are the most -probable ones, so we provide those at the SoC level .dtsi file. - -In practice, in turns out the Armada 370 DB board uses the former, -while the Armada 370 Mirabox uses the latter. - -Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> ---- - arch/arm/boot/dts/armada-370.dtsi | 12 ++++++++++++ - 1 file changed, 12 insertions(+) - ---- a/arch/arm/boot/dts/armada-370.dtsi -+++ b/arch/arm/boot/dts/armada-370.dtsi -@@ -47,6 +47,18 @@ - pinctrl { - compatible = "marvell,mv88f6710-pinctrl"; - reg = <0xd0018000 0x38>; -+ -+ sdio_pins1: sdio-pins1 { -+ marvell,pins = "mpp9", "mpp11", "mpp12", -+ "mpp13", "mpp14", "mpp15"; -+ marvell,function = "sd0"; -+ }; -+ -+ sdio_pins2: sdio-pins2 { -+ marvell,pins = "mpp47", "mpp48", "mpp49", -+ "mpp50", "mpp51", "mpp52"; -+ marvell,function = "sd0"; -+ }; - }; - - gpio0: gpio@d0018100 { |