Searched refs:optimal (Results 1 – 25 of 35) sorted by relevance
12
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_KHR_cooperative_matrix.asciidoc | 26 this approach often does not make it possible to write optimal kernels and
|
| D | VK_EXT_multisampled_render_to_single_sampled.adoc | 94 the end of a pass with a format will be optimal on hardware:
101 VkBool32 optimal;
180 multisampled-render-to-single-sampled attachment for optimal performance:
370 Render passes remain the optimal solution for tiling GPUs.
|
| D | VK_EXT_host_image_copy.adoc | 14 Copying data to optimal-layout images in Vulkan requires staging the data in a buffer first, and us…
15 Similarly, copying data out of an optimal-layout image requires a copy to a buffer.
29 While copying to an optimal layout image on the CPU has its own costs, this extension can still lea…
228 Images in optimal layout are often swizzled non-linearly.
|
| D | VK_KHR_maintenance5.adoc | 61 Some tile-based GPUs can benefit from providing an optimal render area granularity as the basis for…
|
| D | VK_EXT_graphics_pipeline_library.adoc | 45 due to sub-optimal linking, and the solution should provide a way to mitigate this.
400 more optimal pipeline layout to be used when generating the final pipeline.
|
| D | VK_EXT_mesh_shader.adoc | 275 …less the performance cost of doing so outweighs the gains of hitting the optimal paths in the impl…
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | VK_NV_optical_flow.adoc | 52 // Check feature support for optimal tiling
|
| D | VK_KHR_depth_stencil_resolve.adoc | 33 give sub-optimal performance.
|
| D | VK_KHR_maintenance5.adoc | 53 * A function flink:vkGetRenderingAreaGranularityKHR to query the optimal
|
| D | VK_NV_win32_keyed_mutex.adoc | 65 // layer, and VK_SAMPLE_COUNT_1_BIT using optimal tiling and supporting
|
| D | VK_NV_external_memory_win32.adoc | 114 // layer, and VK_SAMPLE_COUNT_1_BIT using optimal tiling and supporting
|
| D | VK_EXT_image_drm_format_modifier.adoc | 184 optimal _modifier_ in consideration with the other image parameters.
192 The implementation chooses for the image an optimal _modifier_ from
|
| D | VK_KHR_swapchain.adoc | 199 This could be useful to allow the application to create an "`optimal`"
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_GGP_stream_descriptor_surface/ |
| D | platformCreateSurface_streamdescriptor.adoc | 55 The pname:currentExtent will reflect the current optimal resolution.
|
| /hardware/interfaces/light/2.0/ |
| D | types.hal | 63 * For an optimal HMD viewing experience, the display must meet the following
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_QNX_external_memory_screen_buffer/ |
| D | qnx_screen_buffer.adoc | 66 enabled, and must: have optimal tiling.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
| D | VK_EXT_debug_report.adoc | 96 potentially non-optimal use of Vulkan, e.g. using
|
| D | fault_handling.adoc | 90 * ename:VK_FAULT_LEVEL_WARNING A fault that indicates a non-optimal
|
| D | limits.adoc | 112 optimal image resources can: be bound to adjacent offsets in the same
807 pname:optimalBufferCopyOffsetAlignment is the optimal buffer offset
817 This value is also the optimal host memory offset alignment in bytes for
821 should: use the optimal alignment for optimal performance and power use.
824 pname:optimalBufferCopyRowPitchAlignment is the optimal buffer row pitch
834 This value is also the optimal host memory row pitch alignment in bytes
840 should: use the optimal alignment for optimal performance and power use.
1926 implementation for optimal performance.
1932 implementation for optimal performance.
|
| D | capabilities.adoc | 881 To obtain optimal Android hardware buffer usage flags for specific image
982 Layout not being identical yet still considered optimal for device access
|
| D | VK_EXT_debug_utils.adoc | 581 potentially non-optimal use of Vulkan, e.g. using
|
| D | video_decode_extensions.adoc | 182 output picture and the DPB requires optimal tiling, this avoids the need for
|
| D | memory.adoc | 720 // Try to find an optimal memory type, or if it does not exist try fallback memory type
4121 [[memory-external-android-hardware-buffer-optimal-usages]]
4135 to flink:vkGetPhysicalDeviceImageFormatProperties2 to obtain optimal Android
4166 sampled images, and must: have optimal tiling.
|
| /hardware/interfaces/graphics/composer/2.4/ |
| D | IComposerClient.hal | 302 * supported, this signal should switch the display to a mode that is optimal for the given
|
| /hardware/interfaces/camera/metadata/3.2/ |
| D | types.hal | 288 * of this capture, to help the camera device to decide optimal 3A
|
12