diff options
| author | Bas Nieuwenhuizen <[email protected]> | 2019-04-17 01:30:49 +0200 |
|---|---|---|
| committer | Bas Nieuwenhuizen <[email protected]> | 2019-04-23 23:49:39 +0000 |
| commit | f2e0f5c3c44967da8a10ac363ab667e07ea03c28 (patch) | |
| tree | 7798bceec1b829068e63267d67f423288759f75e /src/intel/vulkan | |
| parent | 3c2e8267d0b2300963d9a04aa4c46058ef448e49 (diff) | |
vulkan/wsi: Add X11 adaptive sync support based on dri options.
The dri options are optional. When the dri options are not provided
the WSI will not use adaptive sync.
FWIW I think for xf86-video-amdgpu this still requires an X11 config
option, so only people who opt in can get possible regressions from this.
So then the remaining question is: why do this in the WSI?
It has been suggested in another MR that the application sets this.
However, I disagree with that as I don't think we'll ever get a
reasonable set of applications setting it.
The next questions is whether this can be a layer. It definitely
can be as implemented now. However, I think this generally fits
well with the function of the WSI. Furthemore, for e.g. the DISPLAY
WSI this is much harder to do in a layer.
Of course, most of the WSI could almost be a layer, but I think
this still fits best in the WSI.
Acked-by: Jason Ekstrand <[email protected]>
Diffstat (limited to 'src/intel/vulkan')
| -rw-r--r-- | src/intel/vulkan/anv_wsi.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/src/intel/vulkan/anv_wsi.c b/src/intel/vulkan/anv_wsi.c index 024bc1c245d..ba07bcef8b3 100644 --- a/src/intel/vulkan/anv_wsi.c +++ b/src/intel/vulkan/anv_wsi.c @@ -49,7 +49,8 @@ anv_init_wsi(struct anv_physical_device *physical_device) anv_physical_device_to_handle(physical_device), anv_wsi_proc_addr, &physical_device->instance->alloc, - physical_device->master_fd); + physical_device->master_fd, + NULL); if (result != VK_SUCCESS) return result; |