Searched refs:subpasses (Results 1 – 24 of 24) sorted by relevance
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
D | VK_EXT_subpass_merge_feedback.adoc | 12 The Vulkan render pass mechanism allows the implementation to merge subpasses at render pass 15 has no way to know which (if any) subpasses were merged. 17 For performance debugging, applications may want to query whether certain subpasses were 19 for certain subpasses, in order to determine the impact of subpass merging on performance. 29 If the subpasses cannot be merged, the reason could be returned. The driver could change the 72 tell application which subpasses are merged.
|
D | VK_EXT_shader_tile_image.adoc | 10 …s supporting this extension, it is a replacement for many use-cases for subpasses, which are not a… 23 …ted `VK_KHR_dynamic_rendering`, which offers an alternative API without subpasses. But keeping dat… 25 This proposal aims to provide the most essential functionality of subpasses, but in an explicit man… 38 …eason about performance expectations, for the same reasons that it is hard to do this for subpasses 72 * Many use-cases that benefit from subpasses could be implemented with this functionality 285 …tile image feature with raster order access enabled are expected to match the gains from subpasses. 469 … to be able to access framebuffer data. The input attachments in Vulkan subpasses help these GPU i…
|
D | VK_QCOM_tile_properties.adoc | 56 …f merged subpasses, and each tile property is associated with a merged subpass. There will be at m… 174 …set of dimensions for tile size so how to handle the case of non-merged subpasses where each subpa…
|
D | VK_KHR_dynamic_rendering.adoc | 19 . Most applications do not or cannot use subpasses, but still pay the cost of setting them up 26 …single pass render passes; additional functionality to replace multiple subpasses will be in a sep… 428 Without multiple subpasses the view mask is significantly less useful; the layer count provided is … 432 === Should we have functionality to replace the on-chip storage aspect of subpasses?
|
D | VK_EXT_legacy_dithering.adoc | 96 execute the two subpasses on the tile, without implicit splits such as due
|
D | VK_EXT_graphics_pipeline_library.adoc | 699 This could be made to work with subpasses with no attachments, but the additional complexity of add…
|
/hardware/google/gfxstream/guest/mesa/src/vulkan/runtime/ |
D | vk_render_pass.c | 84 VK_MULTIALLOC_DECL(&ma, VkSubpassDescription2, subpasses, in vk_common_CreateRenderPass() 138 subpasses[i] = (VkSubpassDescription2) { in vk_common_CreateRenderPass() 152 subpasses[i].viewMask = multiview_info->pViewMasks[i]; in vk_common_CreateRenderPass() 155 subpasses[i].pInputAttachments = reference_ptr; in vk_common_CreateRenderPass() 157 subpasses[i].inputAttachmentCount, in vk_common_CreateRenderPass() 160 subpasses[i].pColorAttachments = reference_ptr; in vk_common_CreateRenderPass() 162 subpasses[i].colorAttachmentCount, in vk_common_CreateRenderPass() 165 subpasses[i].pResolveAttachments = NULL; in vk_common_CreateRenderPass() 167 subpasses[i].pResolveAttachments = reference_ptr; in vk_common_CreateRenderPass() 169 subpasses[i].colorAttachmentCount, in vk_common_CreateRenderPass() [all …]
|
D | vk_render_pass.h | 281 struct vk_subpass *subpasses; member
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
D | VK_HUAWEI_subpass_shading.adoc | 151 VkSubpassDescription2 subpasses[] = { 205 sizeof(subpasses)/sizeof(subpasses[0]), subpasses,
|
D | VK_EXT_subpass_merge_feedback.adoc | 21 whether the subpasses specified on render pass creation are merged by the
|
D | VK_EXT_color_write_enable.adoc | 25 between subpasses or bandwidth savings for unused outputs.
|
D | VK_EXT_multisampled_render_to_single_sampled.adoc | 73 3) There is no guarantee that multisampled data between two subpasses with 82 multisampled-render-to-single-sampled subpasses to potentially execute more
|
D | VK_QCOM_fragment_density_map_offset.adoc | 92 // Offsets given in other subpasses are ignored
|
D | VK_NVX_multiview_per_view_attributes.adoc | 26 subpasses, where the attributes for all views are written out by a single
|
D | VK_KHR_maintenance2.adoc | 64 Consider the case where a render pass has two subpasses and two attachments.
|
D | glossary.adoc | 102 a framebuffer attachment that is accessed by one or more subpasses. 1397 later subpasses and whose contents must: be preserved through this 1748 An execution and/or memory dependency between two subpasses described as 1750 subpasses in a render pass instance. 1752 subpasses, and can: provide guarantees of memory coherence between 1753 accesses in the subpasses.
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
D | renderpass.adoc | 1203 definition of framebuffer-local dependencies between multiple subpasses. 1262 A render pass object represents a collection of attachments, subpasses, and 1263 dependencies between the subpasses, and describes how the attachments are 1264 used over the course of the subpasses. 1320 The subpasses in a render pass all render to the same dimensions, and 1322 contents written by previous subpasses at that same (x,y,layer) location. 1334 By describing a complete set of subpasses in advance, render passes provide 1336 attachment data between subpasses. 1338 In practice, this means that subpasses with a simple framebuffer-space 1346 and memory dependencies>> between subpasses. [all …]
|
D | framebuffer.adoc | 1113 merged subpasses, and each tile property is associated with a merged 1115 There will be at most as many properties as there are subpasses within the
|
D | vertexpostproc.adoc | 1178 primitives for all subpasses of the render pass.
|
D | queries.adoc | 555 Queries used with multiview rendering must: not span subpasses, i.e. they
|
D | synchronization.adoc | 1737 and destination subpasses in the corresponding synchronization scopes. 1829 recorded to other subpasses.
|
D | devsandqueues.adoc | 447 maximum number of subpasses in a render pass.
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_EXT_subpass_merge_feedback/ |
D | renderpass.adoc | 32 merging the described subpass with previous subpasses in the render pass.
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/ |
D | ChangeLog.adoc | 6455 * Clarify usable sample counts for empty subpasses in the 10077 * Define how framebuffer-local dependencies work between subpasses with
|