Jon Leech 5abf83f95d Change log for April 16, 2019 Vulkan 1.1.107 spec update:
* Update release number to 107.

Public Issues:

  * Fix revision date for the `<<VK_AMD_gpu_shader_half_float>>` appendix
    (public issue 617).
  * Make <<synchronization-pipeline-barriers-subpass-self-dependencies,
    subpass self-dependencies>> less restrictive (public issue 777).
  * Fix the `<<VK_EXT_full_screen_exclusive>>` dependency on
    `<<VK_KHR_win32_surface>>` in `vk.xml` (public pull request 849).
  * Remove single-page (`apispec.html`) refpage sub-targets from the
    Makefile `allman` target and the build instructions. The target is still
    present in the Makefile, but we have not been actively maintaining the
    single-page document and do not promise it will work. The full
    Specification and the individual API reference pages are what we support
    and publish at present (public issue 949).

Internal Issues:

  * De-duplicate common valid usage statements shared by multiple commands
    or structures by using asciidoctor includes and dynamically assigning
    part of the valid usage ID based on which command or structure they're
    being applied to (internal issue 779).
  * Add reference pages for constructs not part of the formal API, such as
    platform calling convention macros, and script changes supporting them
    This required suppressing some check_spec_links warning classes in order
    to pass CI, until a more sophisticated fix can be done (internal issue
    888).
  * Change math notation for the elink:VkPrimitiveTopology descriptions to
    use short forms `v` and `p` instead of `vertex` and `primitive`,
    increasing legibility (internal issue 1611).
  * Rewrite generated file includes relative to a globally specified path,
    fixing some issues with refpage generation (internal issue 1630).
  * Update contributor list for `<<VK_EXT_calibrated_timestamps>>`.
  * Fix use of pathlin in `scripts/generator.py` so the script will work on
    Windows under Python 3.5 (internal merge request 3107).
  * Add missing conditionals around the
    <<descriptorsets-accelerationstructure, Acceleration Structure>>
    section (internal merge request 3108).
  * More script synchronization with OpenXR spec repository (internal merge
    request 3109).
  * Mark the `<<VK_AMD_gpu_shader_half_float>>` and
    `<<VK_AMD_gpu_shader_int16>>` extensions as deprecated in `vk.xml` and
    the corresponding extension appendices (internal merge request 3112).

New Extensions:

  * `<<VK_EXT_headless_surface>>`
2019-04-16 05:19:43 -07:00

52 lines
1.8 KiB
Plaintext

=== Display Control
[open,refpage='vkDisplayPowerControlEXT',desc='Set the power state of a display',type='protos']
--
To set the power state of a display, call:
include::{generated}/api/protos/vkDisplayPowerControlEXT.txt[]
* pname:device is a logical device associated with pname:display.
* pname:display is the display whose power state is modified.
* pname:pDisplayPowerInfo is an instance of slink:VkDisplayPowerInfoEXT
specifying the new power state of pname:display.
include::{generated}/validity/protos/vkDisplayPowerControlEXT.txt[]
--
[open,refpage='VkDisplayPowerInfoEXT',desc='Describe the power state of a display',type='structs']
--
The sname:VkDisplayPowerInfoEXT structure is defined as:
include::{generated}/api/structs/VkDisplayPowerInfoEXT.txt[]
* pname:sType is the type of this structure.
* pname:pNext is `NULL` or a pointer to an extension-specific structure.
* pname:powerState is a elink:VkDisplayPowerStateEXT value specifying the
new power state of the display.
include::{generated}/validity/structs/VkDisplayPowerInfoEXT.txt[]
--
[open,refpage='VkDisplayPowerStateEXT',desc='Possible power states for a display',type='enums']
--
Possible values of slink:VkDisplayPowerInfoEXT::pname:powerState, specifying
the new power state of a display, are:
include::{generated}/api/enums/VkDisplayPowerStateEXT.txt[]
* ename:VK_DISPLAY_POWER_STATE_OFF_EXT specifies that the display is
powered down.
* ename:VK_DISPLAY_POWER_STATE_SUSPEND_EXT specifies that the display is
put into a low power mode, from which it may: be able to transition back
to ename:VK_DISPLAY_POWER_STATE_ON_EXT more quickly than if it were in
ename:VK_DISPLAY_POWER_STATE_OFF_EXT.
This state may: be the same as ename:VK_DISPLAY_POWER_STATE_OFF_EXT.
* ename:VK_DISPLAY_POWER_STATE_ON_EXT specifies that the display is
powered on.
--