diff options
Diffstat (limited to 'target/linux/omap/patches-3.12/797-ARM_dts_omap4-panda-es_Do_not_reset_gpio1.patch')
| -rw-r--r-- | target/linux/omap/patches-3.12/797-ARM_dts_omap4-panda-es_Do_not_reset_gpio1.patch | 26 |
1 files changed, 0 insertions, 26 deletions
diff --git a/target/linux/omap/patches-3.12/797-ARM_dts_omap4-panda-es_Do_not_reset_gpio1.patch b/target/linux/omap/patches-3.12/797-ARM_dts_omap4-panda-es_Do_not_reset_gpio1.patch deleted file mode 100644 index 0bd80e243a..0000000000 --- a/target/linux/omap/patches-3.12/797-ARM_dts_omap4-panda-es_Do_not_reset_gpio1.patch +++ /dev/null @@ -1,26 +0,0 @@ -From c1bac171c4f203101611110869bd2511c8153974 Mon Sep 17 00:00:00 2001 -From: Nishanth Menon <nm@ti.com> -Date: Thu, 10 Oct 2013 16:44:41 +0000 -Subject: ARM: dts: omap4-panda-es: Do not reset gpio1 - -Do not reset GPIO1 at boot-up because GPIO 7 in GPIO1 block is used on -OMAP4460 PandaBoard-ES to select voltage register in TPS62361 which -supplies VDD_MPU. - -Without this, OMAP4460 PandaBoard-ES boards fail to boot-up because -MPU voltage switches over to VSET0 voltage value (boot voltage) which -is not sufficient to operate the device at OPP100. - -Signed-off-by: Nishanth Menon <nm@ti.com> -Signed-off-by: Benoit Cousson <bcousson@baylibre.com> ---- ---- a/arch/arm/boot/dts/omap4-panda-es.dts -+++ b/arch/arm/boot/dts/omap4-panda-es.dts -@@ -62,3 +62,7 @@ - gpios = <&gpio1 8 GPIO_ACTIVE_HIGH>; - }; - }; -+ -+&gpio1 { -+ ti,no-reset-on-init; -+}; |