From ba9142274765869cd58ec0c55e7ef8da0354ed25 Mon Sep 17 00:00:00 2001 From: emersion Date: Fri, 5 Oct 2018 16:14:22 +0200 Subject: output: don't trigger a frame immediately in schedule_frame This desynchronizes our rendering loop with the vblank cycle. In case a compositor doesn't swap buffers but schedules a frame, emitting a frame event immediately enters a busy-loop. Instead, ask the backend to send a frame when appropriate. On Wayland we can just register a frame callback on our surface. On DRM we can do a no-op pageflip. Fixes #617 Fixes swaywm/sway#2748 --- include/wlr/interfaces/wlr_output.h | 1 + 1 file changed, 1 insertion(+) (limited to 'include/wlr/interfaces/wlr_output.h') diff --git a/include/wlr/interfaces/wlr_output.h b/include/wlr/interfaces/wlr_output.h index 52581768..da37cba1 100644 --- a/include/wlr/interfaces/wlr_output.h +++ b/include/wlr/interfaces/wlr_output.h @@ -33,6 +33,7 @@ struct wlr_output_impl { size_t (*get_gamma_size)(struct wlr_output *output); bool (*export_dmabuf)(struct wlr_output *output, struct wlr_dmabuf_attributes *attribs); + void (*schedule_frame)(struct wlr_output *output); }; void wlr_output_init(struct wlr_output *output, struct wlr_backend *backend, -- cgit v1.2.3