[PATCH 5/8] introduce device async resume

[Zhang Rui]

introduce device async resume.

If boot option "dev_async_action" is added,
devices can be resumed asynhronously.

Signed-off-by: Zhang Rui <rui.zhang@xxxxxxxxx>
---
 drivers/base/power/main.c |    4 +++-
 include/linux/async_dev.h |    4 +++-
 drivers/base/async_dev.c        |    1 +
 3 files changed, 7 insertions(+), 2 deletions(-)

Index: linux-2.6/drivers/base/power/main.c
===================================================================
--- linux-2.6.orig/drivers/base/power/main.c
+++ linux-2.6/drivers/base/power/main.c
@@ -445,7 +445,8 @@ static void dpm_resume(pm_message_t stat
 			dev->power.status = DPM_RESUMING;
 			mutex_unlock(&dpm_list_mtx);
 
-			error = device_resume(dev, state);
+			error = dev_async_schedule(dev, device_resume, &state,
+							DEV_ASYNC_RESUME);
 
 			mutex_lock(&dpm_list_mtx);
 			if (error)
@@ -460,6 +461,7 @@ static void dpm_resume(pm_message_t stat
 	}
 	list_splice(&list, &dpm_list);
 	mutex_unlock(&dpm_list_mtx);
+	dev_async_synchronization();
 }
 
 /**
Index: linux-2.6/include/linux/async_dev.h
===================================================================
--- linux-2.6.orig/include/linux/async_dev.h
+++ linux-2.6/include/linux/async_dev.h
@@ -29,7 +29,9 @@ struct dev_async_struct {
 };
 
 #define DEV_ASYNC_SUSPEND	1
-#define DEV_ASYNC_ACTIONS_ALL	DEV_ASYNC_SUSPEND
+#define DEV_ASYNC_RESUME	2
+#define DEV_ASYNC_ACTIONS_ALL	(DEV_ASYNC_SUSPEND |	\
+				DEV_ASYNC_RESUME)
 
 extern int dev_async_schedule(struct device *, void *,
 			void *, int);
Index: linux-2.6/drivers/base/async_dev.c
===================================================================
--- linux-2.6.orig/drivers/base/async_dev.c
+++ linux-2.6/drivers/base/async_dev.c
@@ -36,6 +36,7 @@ static int dev_action(struct device *dev
 
 	switch (type) {
 	case DEV_ASYNC_SUSPEND:
+	case DEV_ASYNC_RESUME:
 		error = ((dev_async_suspend)func)(dev, *((pm_message_t *)data));
 		break;
 	default:


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/