From b0a9d39644c3067495e895a57b9169762b026449 Mon Sep 17 00:00:00 2001
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
Date: Thu, 16 Sep 2010 18:44:48 +0530
Subject: [PATCH] --- yaml --- r: 216885 b: refs/heads/master c:
 e7193cc8e7b67b29483d9fd4fec04ec7b42861f0 h: refs/heads/master i:   216883:
 6b034b1bb55c446909811faa9a57c6567bbe91bb v: v3

---
 [refs]                             | 2 +-
 trunk/arch/arm/plat-omap/dmtimer.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/[refs] b/[refs]
index c85f01d5b2f0..a4cc978d32db 100644
--- a/[refs]
+++ b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: b5be6b66b7a33f48bf0dfb466443ae9b65e69871
+refs/heads/master: e7193cc8e7b67b29483d9fd4fec04ec7b42861f0
diff --git a/trunk/arch/arm/plat-omap/dmtimer.c b/trunk/arch/arm/plat-omap/dmtimer.c
index 44bafdab2dce..1d706cf63ca0 100644
--- a/trunk/arch/arm/plat-omap/dmtimer.c
+++ b/trunk/arch/arm/plat-omap/dmtimer.c
@@ -581,7 +581,7 @@ int omap_dm_timer_set_source(struct omap_dm_timer *timer, int source)
 	 * When the functional clock disappears, too quick writes seem
 	 * to cause an abort. XXX Is this still necessary?
 	 */
-	__delay(150000);
+	__delay(300000);
 
 	return ret;
 }