[RFC/PATCH] arm: oprofile: remove locking from suspend/resume

[Kevin Hilman <khilman@deeprootsystems.com>]

Since oprofile is a sysdev, its suspend/resume methods are called with
interrupts disabled.  Using a mutex (which might sleep) in this atomic
context is not safe.

Since these methods are already called in atomic context, simply
remove the locking in the suspend/resume methods.

Found using lockdep on OMAP3 (Cortex-A8)

Signed-off-by: Kevin Hilman <khilman@deeprootsystems.com>
---
 arch/arm/oprofile/common.c |    4 ----
 1 files changed, 0 insertions(+), 4 deletions(-)

diff --git a/arch/arm/oprofile/common.c b/arch/arm/oprofile/common.c
index 3fcd752..ea005d8 100644
--- a/arch/arm/oprofile/common.c
+++ b/arch/arm/oprofile/common.c
@@ -79,19 +79,15 @@ static void op_arm_stop(void)
 #ifdef CONFIG_PM
 static int op_arm_suspend(struct sys_device *dev, pm_message_t state)
 {
-	mutex_lock(&op_arm_mutex);
 	if (op_arm_enabled)
 		op_arm_model->stop();
-	mutex_unlock(&op_arm_mutex);
 	return 0;
 }
 
 static int op_arm_resume(struct sys_device *dev)
 {
-	mutex_lock(&op_arm_mutex);
 	if (op_arm_enabled && op_arm_model->start())
 		op_arm_enabled = 0;
-	mutex_unlock(&op_arm_mutex);
 	return 0;
 }
 
-- 
1.7.0.2