Searched refs:exact (Results 1 – 25 of 54) sorted by relevance
123
| /hardware/google/pixel-sepolicy/common/system_ext/ |
| D | property_contexts | 1 ro.chipname u:object_r:deprecated_soc_prop:s0 exact string
2 ro.hardware.chipname u:object_r:deprecated_soc_prop:s0 exact string
3 ro.mediatek.platform u:object_r:deprecated_soc_prop:s0 exact string
|
| /hardware/interfaces/automotive/can/1.0/ |
| D | ICanMessageListener.hal | 26 * was received by the hardware. If it's not possible to fetch exact
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | VK_EXT_image_compression_control.adoc | 29 lossless, but the results are typically not bit-exact when compared to a
|
| D | invariance.adoc | 9 The Vulkan specification is not pixel exact.
10 It therefore does not guarantee an exact match between images produced by
12 However, the specification does specify exact matches, in some cases, for
15 those cases that require exact matches.
238 of computing 1.0-x in a tessellation evaluation shader will be exact.
|
| D | VK_KHR_external_semaphore.adoc | 62 However, implementations need not validate handles are of the exact type
|
| D | VK_NV_shading_rate_image.adoc | 77 an exact order?
|
| /hardware/interfaces/camera/provider/2.5/ |
| D | types.hal | 47 * The exact point when this status change happens during the folding
|
| /hardware/interfaces/soundtrigger/2.1/ |
| D | ISoundTriggerHw.hal | 75 * Must have the exact same semantics as loadSoundModel from
109 * Must have the exact same semantics as loadPhraseSoundModel from
140 * Must have the exact same semantics as startRecognition from
|
| /hardware/libhardware/modules/local_time/ |
| D | Android.bp | 20 // if no other device specific modules are present. The exact load order can be
|
| /hardware/libhardware/modules/audio/ |
| D | Android.bp | 16 // device specific modules are present. The exact load order can be seen in
|
| /hardware/interfaces/security/rkp/ |
| D | CHANGELOG.md | 3 This document provides an exact description of which changes have occurred in the
|
| /hardware/google/gfxstream/guest/mesa/src/vulkan/runtime/ |
| D | vk_graphics_state.h | 336 bool exact; member
|
| D | vk_graphics_state.c | 541 .depth_bias.exact = false, in vk_rasterization_state_init()
638 rs->depth_bias.exact = dbr_info->depthBiasExact; in vk_rasterization_state_init()
1931 COPY_IF_SET(RS_DEPTH_BIAS_FACTORS, rs.depth_bias.exact); in vk_dynamic_graphics_state_copy()
2876 rs.depth_bias.exact, dbr_info->depthBiasExact); in vk_common_CmdSetDepthBias2EXT()
2882 rs.depth_bias.exact, false); in vk_common_CmdSetDepthBias2EXT()
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_EXT_image_compression_control.adoc | 15 …tations manage this transparently to applications, which is possible since the output is bit-exact.
20 Since results are generally not bit-exact when compared to an uncompressed result, we do not want i…
|
| D | VK_EXT_depth_bias_control.adoc | 16 …ications and API layering efforts, e.g., D3D9, need a way for depth bias to be represented in exact
|
| D | VK_EXT_pipeline_protected_access.adoc | 82 potential penalty for access to the exact resources that use protected memory.
|
| D | VK_EXT_dynamic_rendering_unused_attachments.adoc | 42 The current restrictions require there to be an exact match between the bound pipeline
|
| D | VK_EXT_shader_module_identifier.adoc | 112 …identical. This will easily contribute to pipeline cache bloat, since the exact same pipelines mig…
|
| /hardware/interfaces/soundtrigger/2.3/ |
| D | ISoundTriggerHw.hal | 47 * Must have the exact same semantics as startRecognition from
|
| /hardware/interfaces/gnss/visibility_control/1.0/ |
| D | IGnssVisibilityControlCallback.hal | 137 * To avoid overly spamming the framework, high speed location reporting of the exact same
|
| /hardware/interfaces/automotive/sv/1.0/ |
| D | ISurroundView3dSession.hal | 99 * 3d points returned are projected on an approximate 3d surface and do not provide the exact
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_QNX_external_memory_screen_buffer/ |
| D | qnx_screen_buffer.adoc | 49 The exact Screen-native usage flags required depends on the Vulkan
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/ |
| D | VK_AMD_shader_info.adoc | 54 The exact formatting and contents of the disassembly string are
|
| /hardware/interfaces/camera/device/3.2/ |
| D | ICameraDevice.hal | 152 * method to check the exact version of callback sent by camera service.
|
| /hardware/interfaces/graphics/common/1.0/ |
| D | types.hal | 95 * The exact pixel layout of the data in the buffer is sensor-dependent, and
219 * contains the 2 least significant bits of the 4 pixels, the exact layout data
274 * byte contains the 4 least significant bits of the two pixels, the exact layout
|
123