Searched refs:areas (Results 1 – 25 of 27) sorted by relevance
12
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
D | VK_QCOM_multiview_per_view_render_areas.adoc | 26 per-view render areas to the implementation. 27 Such per-view render areas can be used by the implementation to reduce the 32 render areas. 59 The per-view render areas are not rotated. 74 5) When per-view render areas are specified, what purpose if any do 85 union of all the per-view render areas.
|
D | VK_EXT_fragment_density_map.adoc | 31 This extension allows an application to specify areas of the render target 36 The primary use of this extension is to reduce workloads in areas where 64 optimize rendering in areas of low density. 66 help to further optimize rendering in areas of low density.
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
D | fragmentdensitymapops.adoc | 133 implementation and must: have an area between the _min_ and _max_ areas of 144 Implementations may: vary the supported set of fragment areas per 152 implementation only supports areas of [eq]#{(1,1),(2,2)}#, it could choose
|
D | renderpass.adoc | 103 If multiview is enabled, and the <<features-multiview-per-view-render-areas, 111 the union of all the per-view render areas. 582 <<features-multiview-per-view-render-areas, 589 render areas. 5919 <<features-multiview-per-view-render-areas, 5927 the union of all the per-view render areas. 6181 <<features-multiview-per-view-render-areas, 6188 render areas. 6410 [open,refpage='VkDeviceGroupRenderPassBeginInfo',desc='Set the initial device mask and render areas… 6415 structure includes a device mask and set of render areas for the render pass [all …]
|
D | clears.adoc | 269 Clears may: have a different set of supported fragment areas than draws.
|
D | fundamentals.adoc | 77 Each device may: advertise one or more heaps, representing different areas 83 Examples of memory areas that may: be available on an implementation
|
D | features.adoc | 6977 …erAreasFeaturesQCOM',desc='Structure describing multiview per view render areas features that can … 6986 * [[features-multiview-per-view-render-areas]] 6988 supports multiview per-view render areas.
|
D | primsrast.adoc | 550 These locations are exact positions, rather than regions or areas, and each 1422 [eq]#B~xy~# are the fragment areas of the fragment shading rates being
|
D | fragops.adoc | 806 order to make transitions between fragment areas with different fragment
|
D | synchronization.adoc | 479 <<fragmentdensitymapops,generate the fragment areas>>. 718 <<fragmentdensitymapops,generate the fragment areas>>.
|
/hardware/qcom/camera/msm8998/QCamera2/HAL/ |
D | QCameraParameters.cpp | 8893 … cam_area_t *areas = (cam_area_t *)malloc(sizeof(cam_area_t) * m_pCapability->max_num_focus_areas); in setFocusAreas() local 8894 if (NULL == areas) { in setFocusAreas() 8898 memset(areas, 0, sizeof(cam_area_t) * m_pCapability->max_num_focus_areas); in setFocusAreas() 8902 areas, in setFocusAreas() 8905 free(areas); in setFocusAreas() 8909 if (validateCameraAreas(areas, num_areas_found) == false) { in setFocusAreas() 8911 free(areas); in setFocusAreas() 8920 areas[0].rect.left == 0 && in setFocusAreas() 8921 areas[0].rect.top == 0 && in setFocusAreas() 8922 areas[0].rect.width == 0 && in setFocusAreas() [all …]
|
D | QCameraParameters.h | 1095 bool validateCameraAreas(cam_area_t *areas, int num_areas);
|
/hardware/interfaces/automotive/vehicle/2.0/ |
D | IVehicleCallback.hal | 53 * @param areaId - bitmask that specifies in which areas the problem has
|
D | types.hal | 63 * Some properties may be associated with particular areas in the vehicle. For example, 1006 * Enable temperature coupling between areas. 1024 * for the affected areas. Any parameters modified as a side effect
|
/hardware/interfaces/automotive/vehicle/aidl/impl/default_config/config/ |
D | README.md | 62 "areas:" [
|
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
D | template.adoc | 45 Typically, this section will be split into subsections describing different areas of the proposal.
|
D | VK_QCOM_tile_properties.adoc | 26 …owing how their fragment density map will be applied and the final fragment areas that will result. 36 …t density maps that will apply in a more direct way to the final fragment areas in use, allowing m…
|
D | VK_KHR_dynamic_rendering.adoc | 220 …l[VkRenderPassBeginInfo] - setting the device mask and setting independent render areas per device.
|
D | VK_KHR_fragment_shading_rate.adoc | 18 …s; though implementations may be able to take advantage of this to reduce workloads in other areas.
|
D | VK_EXT_graphics_pipeline_library.adoc | 608 profiling may be necessary to identify problematic areas.
|
D | VK_KHR_video_queue.adoc | 536 … has to make sure not to assume any particular values in these "shoulder" areas. This is especiall…
|
/hardware/interfaces/security/rkp/ |
D | README.md | 120 The CDDL in the rest of the document will use the '/' operator to show areas
|
/hardware/interfaces/camera/metadata/3.2/ |
D | types.hal | 224 * <p>List of metering areas to use for auto-exposure adjustment.</p> 252 * <p>List of metering areas to use for auto-focus.</p> 279 * <p>List of metering areas to use for auto-white-balance illuminant
|
/hardware/interfaces/graphics/composer/2.2/ |
D | IComposerClient.hal | 238 * completely black. Any areas of the buffer not covered by such content may
|
/hardware/interfaces/graphics/composer/2.1/ |
D | IComposerClient.hal | 1082 * under translucent areas of other layers. The region is in screen space,
|
12