protocol: allow to send a zero output refresh rate

Submitted by Simon Ser on Sept. 29, 2018, 8:28 p.m.

Details

Message ID -MLKPB-wozrSeHVLBM5i6fmOI1LNtUHGU_ktN45swzoBknfQ0EY-fYmmPbsGrJbnOjcUnn0lmgIk-mSkyo-ss0P9TIQqSUxE0Ts4FysA09M=@emersion.fr
State New
Series "protocol: allow to send a zero output refresh rate"
Headers show

Commit Message

Simon Ser Sept. 29, 2018, 8:28 p.m.
Fixed refresh rate doesn't always make sense for all outputs. In case
it's not available or not relevant, allow compositors to send zero.

This is for instance the case for outputs with variable refresh rate
(such as FreeSync) and virtual outputs.

Signed-off-by: Simon Ser <contact@emersion.fr>
---
 protocol/wayland.xml | 4 ++++
 1 file changed, 4 insertions(+)

Patch hide | download patch | download mbox

diff --git a/protocol/wayland.xml b/protocol/wayland.xml
index 141038b..3c2aa3a 100644
--- a/protocol/wayland.xml
+++ b/protocol/wayland.xml
@@ -2447,6 +2447,10 @@ 
 	the output size in the global compositor space. For instance,
 	the output may be scaled, as described in wl_output.scale,
 	or transformed, as described in wl_output.transform.
+
+	The vertical refresh rate can be set to zero if it doesn't make
+	sense for this output (e.g. for outputs with variable refresh
+	rates or virtual outputs).
       </description>
       <arg name="flags" type="uint" enum="mode" summary="bitfield of mode flags"/>
       <arg name="width" type="int" summary="width of the mode in hardware units"/>

Comments

Simon Ser Oct. 26, 2018, 9:15 a.m.
Hi,

What do you think of this patch?

Thanks,

Simon
Simon Ser Nov. 17, 2018, 11:56 p.m.
Bump