Searched refs:granularity (Results 1 – 25 of 48) sorted by relevance
12
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | VK_EXT_host_image_copy.adoc | 67 3) Should there be granularity requirements for image offsets and extents?
69 *RESOLVED*: No granularity requirements, i.e. a granularity of 1 pixel (for
|
| D | VK_NV_shader_image_footprint.adoc | 45 The minimum granularity supported by this extension is 2x2 (for 2D textures)
46 and 2x2x2 (for 3D textures); the maximum granularity is 256x256 (for 2D
76 Only a limited set of granularity values and that set does not support
99 a fixed granularity and accumulate coverage information from the returned
103 granularity, we expect that the footprint image will use 64-bit texels where
173 may return a granularity larger than that requested by the caller, each
|
| D | VK_EXT_provoking_vertex.adoc | 44 1) At what granularity should this state be set?
53 granularity.
|
| D | VK_EXT_legacy_dithering.adoc | 41 granularity, so a change in dither state would necessarily need to cause a
|
| D | VK_EXT_swapchain_maintenance1.adoc | 41 granularity.
|
| D | VK_KHR_external_memory.adoc | 119 image, or global granularity, and semantically it maps pretty well to the
128 granularity rather than image or buffer granularity, which would make an
169 correct granularity.
|
| D | VK_QCOM_multiview_per_view_render_areas.adoc | 44 The granularity returned by flink:vkGetRenderAreaGranularity also applies to
|
| D | VK_KHR_display.adoc | 41 granularity.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/commonvalidity/ |
| D | copy_image_to_buffer_command_buffer_common.adoc | 29 {regionsparam} must: respect the image transfer granularity requirements
|
| D | copy_buffer_to_image_command_buffer_common.adoc | 29 {regionsparam} must: respect the image transfer granularity requirements
|
| D | copy_image_common.adoc | 68 pname:pRegions must: respect the image transfer granularity requirements
73 pname:pRegions must: respect the image transfer granularity requirements
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/build_tests/chapters/commonvalidity/ |
| D | lorem.adoc | 29 {regionsparam} must: respect the image transfer granularity requirements
|
| /hardware/interfaces/audio/2.0/ |
| D | types.hal | 83 int32_t burstSizeFrames; // transfer size granularity in frames
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_EXT_device_fault.adoc | 212 at some other hardware-unit dependent granularity, rather than the precise
214 dependent granularity, along with an associated precision indicator. This information
|
| D | VK_EXT_mesh_shader.adoc | 33 …ut vertices, meaning things like decompressing meshes or acting at any granularity other than vert…
36 …ty that could be interesting - both have access to geometric data at a granularity other than vert…
37 …ey are still rather fixed in terms of inputs, output topology, and the granularity they operate at…
62 This allows things like modifying the level of detail at a fine granularity without the use of tess…
84 …ermine the number of launched mesh shader workgroups at whatever input granularity they want, and …
|
| D | VK_KHR_maintenance5.adoc | 61 Some tile-based GPUs can benefit from providing an optimal render area granularity as the basis for…
184 render area granularity for a render pass instance:
|
| D | VK_EXT_pipeline_protected_access.adoc | 32 protected memory access in pipeline granularity.
|
| D | VK_QCOM_tile_properties.adoc | 30 …t allow implementations to fully describe the tiling grid and reported granularity is based solely…
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
| D | executiongraphs.adoc | 17 finer granularity than would typically be possible with API commands alone.
404 + (pname:count*pname:stride)), at a granularity of pname:stride must:
421 pname:payloadStride)), at a granularity of pname:payloadStride must:
485 pname:infos + (pname:count*pname:stride)), at a granularity of
514 pname:payloadStride)), at a granularity of pname:payloadStride must:
589 pname:infos + (pname:count*pname:stride)), at a granularity of
618 pname:payloadStride)), at a granularity of pname:payloadStride must:
|
| D | textures.adoc | 3098 .Texel footprint granularity values
3150 * The sixth member is an integer identifying the granularity of the
3196 of the texel group identified by the granularity;
3249 and depth of the texel group identified by the granularity;
3256 an 8x8 or 4x4x4 mask using the granularity requested in the instruction.
3258 requested granularity.
3260 returns an integer granularity value that can: be interpreted in the same
3261 manner as the granularity value provided to the instruction to determine the
3265 requested granularity, code:OpImageSampleFootprintNV will use the requested
3266 granularity as-is and return a granularity value of zero.
|
| /hardware/interfaces/audio/5.0/ |
| D | types.hal | 78 /** Transfer size granularity in frames */
|
| /hardware/interfaces/audio/4.0/ |
| D | types.hal | 101 /** Transfer size granularity in frames */
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_KHR_performance_query/ |
| D | queuefamily.adoc | 100 This scope describes the granularity of a performance counter.
|
| /hardware/interfaces/audio/6.0/ |
| D | types.hal | 78 /** Transfer size granularity in frames */
|
| /hardware/interfaces/audio/7.0/ |
| D | types.hal | 79 /** Transfer size granularity in frames */
|
12