Chromium Code Reviews Chromium Code Reviews
Issue 2404513002:
exo: Implement zcr_linux_explicit_synchronization_v1
| OLD | NEW |
|---|---|
| (Empty) | |
| 1 <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.
| |
| 2 | |
| 3 <copyright> | |
| 4 Copyright 2016 The Chromium Authors. | |
| 5 | |
| 6 Permission is hereby granted, free of charge, to any person obtaining a | |
| 7 copy of this software and associated documentation files (the "Software"), | |
| 8 to deal in the Software without restriction, including without limitation | |
| 9 the rights to use, copy, modify, merge, publish, distribute, sublicense, | |
| 10 and/or sell copies of the Software, and to permit persons to whom the | |
| 11 Software is furnished to do so, subject to the following conditions: | |
| 12 | |
| 13 The above copyright notice and this permission notice (including the next | |
| 14 paragraph) shall be included in all copies or substantial portions of the | |
| 15 Software. | |
| 16 | |
| 17 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR | |
| 18 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, | |
| 19 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL | |
| 20 THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER | |
| 21 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING | |
| 22 FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER | |
| 23 DEALINGS IN THE SOFTWARE. | |
| 24 </copyright> | |
| 25 | |
| 26 <description summary="Protocol for explicit synchronization"> | |
| 27 This protocol specifies a set of interfaces used to provide explicit | |
| 28 synchronization of buffers to the the client. | |
| 29 | |
| 30 Warning! The protocol described in this file is experimental and backward | |
| 31 incompatible changes may be made. Backward compatible changes may be added | |
| 32 together with the corresponding interface version bump. Backward | |
| 33 incompatible changes are done by bumping the version number in the protocol | |
| 34 and interface names and resetting the interface version. Once the protocol | |
| 35 is to be declared stable, the version number in the protocol is removed and | |
| 36 the interface version number is reset. | |
| 37 </description> | |
| 38 | |
| 39 <interface name="zcr_linux_explicit_fencing_v1" version="1"> | |
| 40 <description summary="Protocol for providing explicit fencing support"> | |
| 41 The global interface that allows clients to subscribe for explicit | |
| 42 synchronization fences for given wl_surface. | |
| 43 </description> | |
| 44 | |
| 45 <request name="destroy" type="destructor"> | |
| 46 <description summary="destroy explicit fencing object"> | |
| 47 Destroy this explicit synchronization object. Existing explicit | |
| 48 synchronization objects shall not be affected by this request. | |
| 49 </description> | |
| 50 </request> | |
| 51 | |
| 52 <enum name="error"> | |
| 53 <entry name="fencing_exists" value="0" | |
| 54 summary="the surface already has an fencing object associated"/> | |
| 55 </enum> | |
| 56 | |
| 57 <request name="get_surface"> | |
| 58 <description summary="extend surface interface for explicit fencing"> | |
| 59 Instantiate an interface extension for the given wl_surface to | |
| 60 provide explicit fencing. If the given wl_surface already has | |
| 61 an explicit fencing object associated, the fencing_exists | |
| 62 protocol error is raised. | |
| 63 | |
| 64 Please see the zcr_explicit_fenced_surface_v1 protocol description | |
| 65 for details of how this affects the behaviour of the wl_surface it | |
| 66 is created against. | |
| 67 </description> | |
| 68 | |
| 69 <arg name="id" type="new_id" interface="zcr_explicit_fenced_surface_v1" | |
| 70 summary="the new surface-fencing interface id"/> | |
| 71 <arg name="surface" type="object" interface="wl_surface" | |
| 72 summary="the surface"/> | |
| 73 </request> | |
| 74 </interface> | |
| 75 | |
| 76 <interface name="zcr_explicit_fenced_surface_v1" version="1"> | |
| 77 <request name="destroy" type="destructor"> | |
| 78 <description summary="destroy synchronization object"> | |
| 79 Destroy this explicit synchronization object. | |
| 80 </description> | |
| 81 </request> | |
| 82 | |
| 83 <request name="set_acquire_fence"> | |
| 84 <description summary="set the acquire fence"> | |
| 85 Set the acquire fence that must be signaled before the compositor | |
| 86 is allowed to read the pixels in the pending wl_buffer. | |
| 87 | |
| 88 The acquire state is double-buffered state, and will be applied on | |
| 89 the next wl_surface.commit. | |
| 90 </description> | |
| 91 <arg name="fd" type="fd" summary="fence fd"/> | |
| 92 </request> | |
| 93 | |
| 94 <event name="present"> | |
| 95 <description summary="present fence changed"> | |
| 96 Provides client with a fence that will be signaled at the vsync when | |
| 97 the result of composition of last frame appear. | |
| 98 </description> | |
| 99 <arg name="fd" type="fd" summary="fence fd"/> | |
| 100 </event> | |
| 101 </interface> | |
| 102 | |
| 103 </protocol> | |
| OLD | NEW |
