| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_shared_presentable_image/ |
| D | wsi.adoc | 7 ename:VK_PRESENT_MODE_SHARED_CONTINUOUS_REFRESH_KHR, a single presentable
8 image can: be acquired, referred to as a shared presentable image.
9 A shared presentable image may: be concurrently accessed by the application
15 presentable image after a present.
21 shared presentable image during every refresh cycle.
29 The presentation engine may: access a shared presentable image at any time
51 presentable image, call:
66 contents of the shared presentable image, as per the swapchain's
70 contents of the shared presentable image, as per the swapchain's
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_display_swapchain/ |
| D | create_shared_swapchains.adoc | 7 [open,refpage='vkCreateSharedSwapchainsKHR',desc='Create multiple swapchains that share presentable…
15 swapchains that share presentable images are created by calling:
35 presentable images must: match between all the swapchains.
37 presentable image layout or are incompatible in a way that prevents sharing
44 the presentable images can: continue to be used.
|
| D | display_swapchain_present.adoc | 23 assumed to be the entire presentable image.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | VK_KHR_shared_presentable_image.adoc | 31 shared presentable image.
56 3) Should the object representing a shared presentable image be an extension
60 and to allow common functionality between shared and normal presentable
65 *RESOLVED*: Shared presentable image / shared present.
75 6) What should the layout of the shared presentable image be?
77 *RESOLVED*: After acquiring the shared presentable image, the application
104 10) Can the ownership of a shared presentable image be transferred to a
108 It is not possible to transfer ownership of a shared presentable image
|
| D | VK_KHR_swapchain_mutable_format.adoc | 27 presentable images with a different format than the one used to create the
43 This extension requires `VK_KHR_maintenance2` and presentable images of
|
| D | VK_GOOGLE_display_timing.adoc | 27 position their geometry for when the presentable image will be presented to
31 They need to know when presentable images were actually presented, and when
|
| D | VK_KHR_swapchain.adoc | 44 of the presentable images?
48 of the presentable image.
50 2) What operations are allowed on presentable images?
53 creating the presentable image's swapchain.
55 3) Does this extension support MSAA presentable images?
61 multi- sampled image to a single-sampled presentable image prior to
64 4) Does this extension support stereo/multi-view presentable images?
67 The number of views associated with a presentable image is determined by the
69 All presentable images in a given swapchain use the same array size.
71 5) Are the layers of stereo presentable images half-sized?
[all …]
|
| D | VK_KHR_incremental_present.adoc | 30 small portion of the presentable images within a swapchain, since it enables
56 *RESOLVED*: The upper left corner of the presentable image(s) of the
|
| D | VK_KHR_display_swapchain.adoc | 32 The lifetime of presentable images is already complex enough.
39 respecify the mode or create a new swapchain and presentable images.
|
| D | glossary.adoc | 1657 Shared presentable image::
1658 A presentable image created from a swapchain with elink:VkPresentModeKHR
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_swapchain/ |
| D | wsi.adoc | 15 A swapchain is an abstraction for an array of presentable images that are
17 The presentable images are represented by sname:VkImage objects created by
43 The presentable images of a swapchain are owned by the presentation engine.
44 An application can: acquire use of a presentable image from the presentation
46 Use of a presentable image must: occur only after the image is returned by
51 An application can: acquire use of a presentable image with
53 After acquiring a presentable image and before modifying it, the application
66 The presentation engine controls the order in which presentable images are
108 pname:pCreateInfo->minImageCount presentable images.
110 While acquired by the application, presentable images can: be used in any
[all …]
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_xcb_surface/ |
| D | platformCreateSurface_xcb.adoc | 80 when using a swapchain or presentable images created from a
84 their presentable images, and any functions that build or queue command
85 buffers that operate on such presentable images.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_xlib_surface/ |
| D | platformCreateSurface_xlib.adoc | 79 code:Display connection when using a swapchain or presentable images created
83 their presentable images, and any functions that build or queue command
84 buffers that operate on such presentable images.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_EXT_swapchain_maintenance1/ |
| D | SwapchainPresentModeInfo.adoc | 36 updates the shared presentable image according to the behavior of
40 engine may: update the shared presentable image or defer that to its
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_incremental_present/ |
| D | wsi.adoc | 9 that only certain rectangular regions of the presentable images of a
58 layer, of a portion of a presentable image that has changed and must: be
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_GOOGLE_display_timing/ |
| D | queries.adoc | 8 ename:VK_PRESENT_MODE_FIFO_KHR so that presentable images are updated during
15 Stuttering occurs when the geometry for each presentable image is not
23 their geometry for when the presentable image will be displayed to the user.
26 They need to know when presentable images were actually presented, and when
101 This will allow the geometry to be correctly positioned for each presentable
|
| /hardware/google/gfxstream/guest/mesa/src/vulkan/runtime/rmv/ |
| D | vk_rmv_tokens.h | 173 bool presentable; member
|
| D | vk_rmv_exporter.c | 1240 rmt_file_write_bits(data, description->presentable, 130, 130); in rmt_dump_image_resource()
1251 rmt_file_write_bits(data, description->presentable, 306, 306); in rmt_dump_image_resource()
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_GGP_stream_descriptor_surface/ |
| D | platformCreateSurface_streamdescriptor.adoc | 63 pname:currentExtent, the presentable images are scaled to the surface's
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_android_surface/ |
| D | platformCreateSurface_android.adoc | 45 surface's pname:currentExtent, the presentable images will be scaled to the
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_wayland_surface/ |
| D | platformCreateSurface_wayland.adoc | 65 connection when using a swapchain or presentable images created from a
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_display/ |
| D | display.adoc | 535 Vendors may: support displaying a subset of a swapchain's presentable images
540 the presentable images that source pixels will be read from when creating a
543 Vendors may: also support mapping the presentable images`' content to a
551 presentable images and the display mode.
695 * pname:imageExtent is the size of the presentable images to use with the
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_surface/ |
| D | wsi.adoc | 361 by presentable images.
381 * pname:maxImageArrayLayers is the maximum number of layers presentable
397 that all pixels in the presentable images have an alpha value of 1.0.
399 representing the ways the application can: use the presentable images of
415 Supported usage flags of a presentable image when using
942 use the shared presentable image from a swapchain created with
1285 While the pname:format of a presentable image refers to the encoding of each
1588 image, which is referred to as a _shared presentable image_.
1597 image, which is referred to as a _shared presentable image_.
1609 The supported elink:VkImageUsageFlagBits of the presentable images of a
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_KHR_video_queue.adoc | 457 …elated operations, e.g. video decode operations may directly output to presentable swapchain image…
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
| D | fundamentals.adoc | 1383 does not use the same presentable image layout, or is incompatible in a
|