Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(7)

Unified Diff: third_party/wayland-protocols/unstable/explicit-fencing/explicit-fencing-unstable-v1.xml

Issue 2404513002: exo: Implement zcr_linux_explicit_synchronization_v1
Patch Set: Created 4 years, 2 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/wayland-protocols/unstable/explicit-fencing/explicit-fencing-unstable-v1.xml
diff --git a/third_party/wayland-protocols/unstable/explicit-fencing/explicit-fencing-unstable-v1.xml b/third_party/wayland-protocols/unstable/explicit-fencing/explicit-fencing-unstable-v1.xml
new file mode 100644
index 0000000000000000000000000000000000000000..2e4357531d2a0247f89bbd0192ba27dfb5fe379a
--- /dev/null
+++ b/third_party/wayland-protocols/unstable/explicit-fencing/explicit-fencing-unstable-v1.xml
@@ -0,0 +1,103 @@
+<protocol name="linux_explicit_synchronization_unstable_v1">
reveman 2016/10/09 19:03:17 please rebase this CL on https://codereview.chromi
fooishbar 2016/10/12 15:41:56 Done.
+
+ <copyright>
+ Copyright 2016 The Chromium Authors.
+
+ Permission is hereby granted, free of charge, to any person obtaining a
+ copy of this software and associated documentation files (the "Software"),
+ to deal in the Software without restriction, including without limitation
+ the rights to use, copy, modify, merge, publish, distribute, sublicense,
+ and/or sell copies of the Software, and to permit persons to whom the
+ Software is furnished to do so, subject to the following conditions:
+
+ The above copyright notice and this permission notice (including the next
+ paragraph) shall be included in all copies or substantial portions of the
+ Software.
+
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
+ THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
+ FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+ DEALINGS IN THE SOFTWARE.
+ </copyright>
+
+ <description summary="Protocol for explicit synchronization">
+ This protocol specifies a set of interfaces used to provide explicit
+ synchronization of buffers to the the client.
+
+ Warning! The protocol described in this file is experimental and backward
+ incompatible changes may be made. Backward compatible changes may be added
+ together with the corresponding interface version bump. Backward
+ incompatible changes are done by bumping the version number in the protocol
+ and interface names and resetting the interface version. Once the protocol
+ is to be declared stable, the version number in the protocol is removed and
+ the interface version number is reset.
+ </description>
+
+ <interface name="zcr_linux_explicit_fencing_v1" version="1">
+ <description summary="Protocol for providing explicit fencing support">
+ The global interface that allows clients to subscribe for explicit
+ synchronization fences for given wl_surface.
+ </description>
+
+ <request name="destroy" type="destructor">
+ <description summary="destroy explicit fencing object">
+ Destroy this explicit synchronization object. Existing explicit
+ synchronization objects shall not be affected by this request.
+ </description>
+ </request>
+
+ <enum name="error">
+ <entry name="fencing_exists" value="0"
+ summary="the surface already has an fencing object associated"/>
+ </enum>
+
+ <request name="get_surface">
+ <description summary="extend surface interface for explicit fencing">
+ Instantiate an interface extension for the given wl_surface to
+ provide explicit fencing. If the given wl_surface already has
+ an explicit fencing object associated, the fencing_exists
+ protocol error is raised.
+
+ Please see the zcr_explicit_fenced_surface_v1 protocol description
+ for details of how this affects the behaviour of the wl_surface it
+ is created against.
+ </description>
+
+ <arg name="id" type="new_id" interface="zcr_explicit_fenced_surface_v1"
+ summary="the new surface-fencing interface id"/>
+ <arg name="surface" type="object" interface="wl_surface"
+ summary="the surface"/>
+ </request>
+ </interface>
+
+ <interface name="zcr_explicit_fenced_surface_v1" version="1">
+ <request name="destroy" type="destructor">
+ <description summary="destroy synchronization object">
+ Destroy this explicit synchronization object.
+ </description>
+ </request>
+
+ <request name="set_acquire_fence">
+ <description summary="set the acquire fence">
+ Set the acquire fence that must be signaled before the compositor
+ is allowed to read the pixels in the pending wl_buffer.
+
+ The acquire state is double-buffered state, and will be applied on
+ the next wl_surface.commit.
+ </description>
+ <arg name="fd" type="fd" summary="fence fd"/>
+ </request>
+
+ <event name="present">
+ <description summary="present fence changed">
+ Provides client with a fence that will be signaled at the vsync when
+ the result of composition of last frame appear.
+ </description>
+ <arg name="fd" type="fd" summary="fence fd"/>
+ </event>
+ </interface>
+
+</protocol>

Powered by Google App Engine
This is Rietveld 408576698