fdo-mirrors/wayland-protocols
1
0
Fork 0
mirror of https://gitlab.freedesktop.org/wayland/wayland-protocols.git synced 2025-12-20 05:50:09 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge branch 'work/multi-gpu-dmabuf' into 'main'

Browse source 
stable/linux-dmabuf: allow compositors to advertise multiple devices

See merge request wayland/wayland-protocols!268
This commit is contained in:
Xaver Hugl 2025-12-16 11:03:36 +00:00
commit 44c84dc247
1 changed files with 53 additions and 20 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

73
stable/linux-dmabuf/linux-dmabuf-v1.xml
View file

@ -24,7 +24,7 @@
DEALINGS IN THE SOFTWARE. DEALINGS IN THE SOFTWARE.
</copyright> </copyright>
<interface name="zwp_linux_dmabuf_v1" version="5"> <interface name="zwp_linux_dmabuf_v1" version="6">
<description summary="factory for creating dmabuf-based wl_buffers"> <description summary="factory for creating dmabuf-based wl_buffers">
This interface offers ways to create generic dmabuf-based wl_buffers. This interface offers ways to create generic dmabuf-based wl_buffers.
@ -184,7 +184,7 @@
</request> </request>
</interface> </interface>
<interface name="zwp_linux_buffer_params_v1" version="5"> <interface name="zwp_linux_buffer_params_v1" version="6">
<description summary="parameters for creating a dmabuf-based wl_buffer"> <description summary="parameters for creating a dmabuf-based wl_buffer">
This temporary object is a collection of dmabufs and other This temporary object is a collection of dmabufs and other
parameters that together form a single logical buffer. The temporary parameters that together form a single logical buffer. The temporary
@ -394,9 +394,25 @@
<arg name="format" type="uint" summary="DRM_FORMAT code"/> <arg name="format" type="uint" summary="DRM_FORMAT code"/>
<arg name="flags" type="uint" enum="flags" summary="see enum flags"/> <arg name="flags" type="uint" enum="flags" summary="see enum flags"/>
</request> </request>
<request name="set_sampling_device" since="6">
<description summary="set the target device of the wl_buffer">
Set the device the compositor should import the dmabufs to for sampling
in the next create or create_immed request.
To avoid race conditions when the compositor removes a device from the
tranches, it is not a protocol error if the device hasn't been advertised
by the compositor in a tranche with the sampling flag, but the import is
likely to fail in that case.
If the client doesn't know a suitable target device, it shouldn't set one,
and the compositor should attempt import on all devices it supports.
</description>
<arg name="device" type="array" summary="device dev_t value"/>
</request>
</interface> </interface>
<interface name="zwp_linux_dmabuf_feedback_v1" version="5"> <interface name="zwp_linux_dmabuf_feedback_v1" version="6">
<description summary="dmabuf feedback"> <description summary="dmabuf feedback">
This object advertises dmabuf parameters feedback. This includes the This object advertises dmabuf parameters feedback. This includes the
preferred devices and the supported formats/modifiers. preferred devices and the supported formats/modifiers.
@ -419,10 +435,13 @@
descending order of preference. All formats and modifiers in the same descending order of preference. All formats and modifiers in the same
tranche have the same preference. tranche have the same preference.
To send parameters, the compositor sends one main_device event, tranches To send parameters, the compositor sends one main_device event (unless
(each consisting of one tranche_target_device event, one tranche_flags the client bound version 6 or above), tranches (each consisting of one
event, tranche_formats events and then a tranche_done event), then one tranche_target_device event, one tranche_flags event, tranche_formats
done event. events and then a tranche_done event), then one done event.
With version 6 and above, the compositor must always advertise at least
one tranche with the sampling flag set.
</description> </description>
<request name="destroy" type="destructor"> <request name="destroy" type="destructor">
@ -463,7 +482,7 @@
<arg name="size" type="uint" summary="table size, in bytes"/> <arg name="size" type="uint" summary="table size, in bytes"/>
</event> </event>
<event name="main_device"> <event name="main_device" deprecated-since="6">
<description summary="preferred main device"> <description summary="preferred main device">
This event advertises the main device that the server prefers to use This event advertises the main device that the server prefers to use
when direct scan-out to the target device isn't possible. The when direct scan-out to the target device isn't possible. The
@ -488,6 +507,9 @@
If explicit modifiers are not supported and the client performs buffer If explicit modifiers are not supported and the client performs buffer
allocations on a different device than the main device, then the client allocations on a different device than the main device, then the client
must force the buffer to have a linear layout. must force the buffer to have a linear layout.
With version 6 and above, this event is no longer sent. Clients should
use a device with the sampling flag in the tranches instead.
</description> </description>
<arg name="device" type="array" summary="device dev_t value"/> <arg name="device" type="array" summary="device dev_t value"/>
</event> </event>
@ -516,9 +538,9 @@
The client can use this hint to allocate the buffer in a way that makes The client can use this hint to allocate the buffer in a way that makes
it accessible from the target device, ideally directly. The buffer must it accessible from the target device, ideally directly. The buffer must
still be accessible from the main device, either through direct import still be accessible from a device with the sampling flag, either through
or through a potentially more expensive fallback path. If the buffer direct import or a potentially more expensive fallback path. If the
can't be directly imported from the main device then clients must be buffer can't be directly imported for sampling, then clients must be
prepared for the compositor changing the tranche priority or making prepared for the compositor changing the tranche priority or making
wl_buffer creation fail (see the wp_linux_buffer_params.create and wl_buffer creation fail (see the wp_linux_buffer_params.create and
create_immed requests for details). create_immed requests for details).
@ -564,19 +586,30 @@
</event> </event>
<enum name="tranche_flags" bitfield="true"> <enum name="tranche_flags" bitfield="true">
<entry name="scanout" value="1" summary="direct scan-out tranche"/> <entry name="scanout" value="1" since="4">
<description summary="direct scan-out tranche">
The scanout flag is a hint that direct scan-out may be attempted by
the compositor on the target device if the client appropriately
allocates a buffer. How to allocate a buffer that can be scanned out
on the target device is implementation-defined.
</description>
</entry>
<entry name="sampling" value="2" since="6">
<description summary="sampling tranche">
The sampling flag describes that the compositor is able to efficiently
sample from buffers imported to the target device if the client
appropriately allocates a buffer. How to allocate a buffer that can be
efficiently sampled on the target device is implementation defined.
</description>
</entry>
</enum> </enum>
<event name="tranche_flags"> <event name="tranche_flags">
<description summary="tranche flags"> <description summary="tranche flags">
This event sets tranche-specific flags. This event sets tranche-specific flags. This event is tied to a
preference tranche, see the tranche_done event.
The scanout flag is a hint that direct scan-out may be attempted by the With version 6 and above, the compositor must set at least one flag
compositor on the target device if the client appropriately allocates a in each tranche.
buffer. How to allocate a buffer that can be scanned out on the target
device is implementation-defined.
This event is tied to a preference tranche, see the tranche_done event.
</description> </description>
<arg name="flags" type="uint" enum="tranche_flags" summary="tranche flags"/> <arg name="flags" type="uint" enum="tranche_flags" summary="tranche flags"/>
</event> </event>