From 94c5339d94c5ae02fe728d6fa74e3812c160d366 Mon Sep 17 00:00:00 2001
From: SooChan Lim <sc1.lim@samsung.com>
Date: Wed, 13 May 2020 19:43:54 +0900
Subject: [PATCH] change the tizen-hwc protocol

The tizen_hwc interface has the commit_feedback request and
tizen_hwc_commit_feedback interface instead of the commit request.
The tizen_hwc_commit_feedback interface can get the hwc committed/discarded events.

Change-Id: I5514c674bd59fdeb9b0aae57dd6bc7be4de1de5f
---
 protocol/tizen/tizen-hwc.xml | 42 +++++++++++++++++++++++++++---------
 1 file changed, 32 insertions(+), 10 deletions(-)

diff --git a/protocol/tizen/tizen-hwc.xml b/protocol/tizen/tizen-hwc.xml
index b8faf43..95dc034 100644
--- a/protocol/tizen/tizen-hwc.xml
+++ b/protocol/tizen/tizen-hwc.xml
@@ -1,20 +1,42 @@
 <protocol name="tizen_hwc">
   <interface name="tizen_hwc" version="1">
-    <request name="commit">
-      <description summary="">
-        Request a notification when a display server requests a hwc_commit to the device.
-        This request is a tizen-specific one. The client wants to know about when a
-        display server requests all displaying requests to the Hardware. In this case,
-        the display server has to send wl_callback done event to the client after a hwc_commit
-        is excuted when it gets the commit request from the client.
-      </description>
-      <arg name="callback" type="new_id" interface="wl_callback" summary="callback object for the commit request"/>
-    </request>
+    <description summary="">
+    </description>
 
     <request name="destroy" type="destructor">
       <description summary="destroy tizen_hwc">
         Destroy tizen_hwc.
       </description>
     </request>
+
+    <request name="commit_feedback">
+      <description summary="">
+        Request a notification when a display server requests a hwc_commit to the device(Hardware).
+        This request is a tizen-specific one. The client wants to know when a display server
+        executes the requests of the wl_surface to the device. In this case, the display server
+        has to send committed event to the client on tizen_commit_feedback interface after it
+        executed the hwc_commit to the device.
+      </description>
+      <arg name="surface" type="object" interface="wl_surface" summary="target surface object"/>
+      <arg name="id" type="new_id" interface="tizen_hwc_commit_feedback" summary="new feedback object"/>
+      <arg name="serial" type="uint" summary="serial number of request"/>
+    </request>
+  </interface>
+
+  <interface name="tizen_hwc_commit_feedback" version="1">
+    <description summary="">
+    </description>
+    <event name="committed">
+      <description summary="hwc commit was executed">
+        The notification event when a display server executed the hwc commit to the device.
+      </description>
+      <arg name="serial" type="uint" summary="serial number of commit request"/>
+    </event>
+    <event name="discarded">
+      <description summary="hwc commit was not executed">
+        The notification event when a display server didn't execute the hwc commit to the device.
+      </description>
+      <arg name="serial" type="uint" summary="serial number of commit request"/>
+    </event>
   </interface>
 </protocol>
-- 
2.34.1