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