VK_EXT_display_control(3)

# VK_EXT_display_control(3) Manual Page

## Name

VK_EXT_display_control - device extension

Loading… please wait.

## Registered Extension Number

92

## Revision

1

## Extension and Version Dependencies

VK_EXT_display_surface_counter
and
VK_KHR_swapchain

## Contact

- James Jones cubanismo

## Other Extension Metadata

Last Modified Date

  2016-12-13

IP Status

  No known IP claims.

Contributors

  - Pierre Boudier, NVIDIA

  - James Jones, NVIDIA

  - Damien Leone, NVIDIA

  - Pierre-Loup Griffais, Valve

  - Daniel Vetter, Intel

## Description

This extension defines a set of utility functions for use with the `VK_KHR_display` and `VK_KHR_display_swapchain` extensions.

## New Commands

- vkDisplayPowerControlEXT

- vkGetSwapchainCounterEXT

- vkRegisterDeviceEventEXT

- vkRegisterDisplayEventEXT

## New Structures

- VkDeviceEventInfoEXT

- VkDisplayEventInfoEXT

- VkDisplayPowerInfoEXT

- Extending VkSwapchainCreateInfoKHR:

  - VkSwapchainCounterCreateInfoEXT

## New Enums

- VkDeviceEventTypeEXT

- VkDisplayEventTypeEXT

- VkDisplayPowerStateEXT

## New Enum Constants

- `VK_EXT_DISPLAY_CONTROL_EXTENSION_NAME`

- `VK_EXT_DISPLAY_CONTROL_SPEC_VERSION`

- Extending VkStructureType:

  - `VK_STRUCTURE_TYPE_DEVICE_EVENT_INFO_EXT`

  - `VK_STRUCTURE_TYPE_DISPLAY_EVENT_INFO_EXT`

  - `VK_STRUCTURE_TYPE_DISPLAY_POWER_INFO_EXT`

  - `VK_STRUCTURE_TYPE_SWAPCHAIN_COUNTER_CREATE_INFO_EXT`

## Issues

1) Should this extension add an explicit “WaitForVsync” API or a fence signaled at vsync that the application can wait on?

RESOLVED: A fence. A separate API could later be provided that allows exporting the fence to a native object that could be inserted into standard run loops on POSIX and Windows systems.

2) Should callbacks be added for a vsync event, or in general to monitor events in Vulkan?

RESOLVED: No, fences should be used. Some events are generated by interrupts which are managed in the kernel. In order to use a callback provided by the application, drivers would need to have the userspace driver spawn threads that would wait on the kernel event, and hence the callbacks could be difficult for the application to synchronize with its other work given they would arrive on a foreign thread.

3) Should vblank or scanline events be exposed?

RESOLVED: Vblank events. Scanline events could be added by a separate extension, but the latency of processing an interrupt and waking up a userspace event is high enough that the accuracy of a scanline event would be rather low. Further, per-scanline interrupts are not supported by all hardware.

## Version History

- Revision 1, 2016-12-13 (James Jones)

  - Initial draft

## See Also

VkDeviceEventInfoEXT, VkDeviceEventTypeEXT, VkDisplayEventInfoEXT, VkDisplayEventTypeEXT, VkDisplayPowerInfoEXT, VkDisplayPowerStateEXT, VkSwapchainCounterCreateInfoEXT, vkDisplayPowerControlEXT, vkGetSwapchainCounterEXT, vkRegisterDeviceEventEXT, vkRegisterDisplayEventEXT

## Document Notes

For more information, see the Vulkan Specification

This page is a generated document. Fixes and changes should be made to the generator scripts, not directly.

## Copyright

Copyright 2014-2023 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0