Upstream version 7.36.149.0

[platform/framework/web/crosswalk.git] / src / third_party / cros_system_api / dbus / power_manager / suspend.proto

diff --git a/src/third_party/cros_system_api/dbus/power_manager/suspend.proto b/src/third_party/cros_system_api/dbus/power_manager/suspend.proto
index ef8ec80..e93d406 100644 (file)
--- a/src/third_party/cros_system_api/dbus/power_manager/suspend.proto
+++ b/src/third_party/cros_system_api/dbus/power_manager/suspend.proto
@@ -8,26 +8,6 @@ option optimize_for = LITE_RUNTIME;
 
 package power_manager;
 
-// Included in powerd's SuspendStateChanged signal, sent when the system is
-// suspending or has just resumed.  The SUSPEND_TO_MEMORY notification may
-// arrive after the subsequent resume.
-message SuspendState {
-  // Next ID to use: 3
-
-  // Type of event.
-  enum Type {
-    SUSPEND_TO_MEMORY = 0;
-    RESUME = 1;
-  }
-  optional Type type = 1;
-
-  // Wall time at which this event occurred, as given by
-  // base::Time::ToInternalValue().  (base::Time is used because the monotonic
-  // clock used by base::TimeTicks doesn't advance while the system is
-  // suspended.)
-  optional int64 wall_time = 2;
-}
-
 // Included in powerd's SuspendImminent signal, sent when the system is about to
 // suspend.  If any clients previously called RegisterSuspendDelay, suspending
 // will be deferred until they've called powerd's HandleSuspendReadiness method.
@@ -35,18 +15,21 @@ message SuspendState {
 // The general flow is as follows:
 //
 // 1. A client that needs to perform some work before the system can be
-//    suspended listens for SuspendImminent messages from powerd.
+//    suspended listens for SuspendImminent and SuspendDone signals from powerd.
 // 2. The client passes a RegisterSuspendDelayRequest to powerd's
 //    RegisterSuspendDelay method and receives a RegisterSuspendDelayReply in
 //    response.  The client saves the |delay_id| field from the response.
 // 3. When the power manager is about to suspend the system, it emits a
 //    SuspendImminent signal containing this message.
 // 4. Upon receipt of the signal, the client performs any last minute work
-//    that it needs to do and then calls powerd's HandleSuspendReadiness,
-//    including its client ID and the |suspend_id| field from the signal.
+//    that it needs to do and then calls powerd's HandleSuspendReadiness method,
+//    including its |delay_id| and the |suspend_id| field from the signal.
 // 5. Once powerd has received notification that all registered clients are
 //    ready to suspend, the system will be suspended.
-// 6. Before the client exits, it calls UnregisterSuspendDelayRequest with its
+// 6. After the system resumes (or the suspend attempt fails or is canceled),
+//    powerd emits a SuspendDone signal. The client may undo any pre-suspend
+//    work that was done in response to the SuspendImminent signal.
+// 7. Before the client exits, it calls UnregisterSuspendDelayRequest with its
 //    delay ID.
 message SuspendImminent {
   // Next ID to use: 2
@@ -56,6 +39,21 @@ message SuspendImminent {
   optional int32 suspend_id = 1;
 }
 
+// Included in powerd's SuspendDone signal, sent after the system has completed
+// a suspend attempt (either by suspending and resuming or by failing to
+// suspend). Each SuspendImminent signal will be followed by a SuspendDone
+// signal.
+message SuspendDone {
+  // Next ID to use: 3
+
+  // Unique ID corresponding to the suspend attempt.
+  optional int32 suspend_id = 1;
+
+  // Wall time that the system was suspended, as given by
+  // base::TimeDelta::ToInternalValue().
+  optional int64 suspend_duration = 2;
+}
+
 // Included in calls to powerd's RegisterSuspendDelay method.
 message RegisterSuspendDelayRequest {
   // Next ID to use: 3