| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/ |
| D | VK_EXT_rgba10x6_formats.adoc | 28 1) Should we reuse the existing format enumeration or introduce a new one?
30 *RESOLVED*: We reuse an existing format enumeration,
35 bit representation as the existing token, but without the limitations.
|
| D | VK_NV_mesh_shader.adoc | 27 It is an alternative to the existing programmable primitive shading
107 . Should we use existing vkCmdDraw or introduce new functions?
113 shading`" chapter, less "`dual use`" language about existing functions
115 The text around the existing "`draws`" is heavily based around emitting
|
| D | VK_EXT_validation_cache.adoc | 23 similarly to the existing slink:VkPipelineCache.
|
| D | VK_EXT_astc_decode_mode.adoc | 16 The existing specification requires that low dynamic range (LDR) ASTC
26 The goal of this extension is to enable this efficiency gain on existing
|
| D | VK_KHR_present_wait.adoc | 41 2) Should this use fences or other existing synchronization mechanism.
66 This is also the 'natural' consequence of interpreting the existing
|
| D | VK_ANDROID_external_memory_android_hardware_buffer.adoc | 85 the output of existing unmodified applications.
89 without causing compatibility problems for existing OpenGL ES applications
121 formats/usages and existing Vulkan features.
133 The extension will only document how existing Vulkan features map to that
|
| D | VK_INTEL_shader_integer_functions2.adoc | 26 Many of these instructions have pre-existing counterparts in the Kernel
|
| D | VK_EXT_shader_image_atomic_int64.adoc | 27 This extension extends existing 64-bit integer atomic support to enable
|
| D | VK_NV_inherited_viewport_scissor.adoc | 47 easy integration into existing applications.
79 least in the short term), we ultimately chose to continue using the existing
|
| D | VK_KHR_surface_protected_capabilities.adoc | 34 It extends the existing slink:VkSurfaceCapabilities2KHR structure with a new
|
| D | VK_NV_linear_color_attachment.adoc | 25 existing elink:VkFormatFeatureFlagBits2KHR bits.
|
| D | VK_KHR_ray_query.adoc | 65 easier for applications to incrementally add ray traced effects to existing
121 ** `apiext:VK_KHR_ray_query` (for ray queries in existing shader stages)
|
| D | VK_EXT_custom_border_color.adoc | 57 *RESOLVED*: Will reuse existing VkClearColorValue structure in order to
86 *RESOLVED*: Separating these does not make much sense as the existing fixed
|
| D | VK_EXT_metal_objects.adoc | 27 Vulkan objects, and supports importing the appropriate existing Metal
|
| /hardware/interfaces/audio/core/all-versions/vts/functional/ |
| D | DeviceManager.h | 47 auto existing = instances.find(name); in getExisting() local
48 return existing != instances.end() ? existing->second : sp<Interface>(); in getExisting()
52 auto existing = instances.find(name); in get() local
53 if (existing != instances.end()) return existing->second; in get()
|
| /hardware/google/gfxstream/third-party/fuchsia/magma/ |
| D | README.md | 5 using some basic heuristics. This will overwrite any existing modifications to
21 codegen succeeded, the files should be moved to replace their existing
|
| /hardware/interfaces/audio/aidl/default/ |
| D | Module.cpp | 1000 auto existing = patches.end(); in setAudioPatch() local
1003 existing = findById<AudioPatch>(patches, in_requested.id); in setAudioPatch()
1004 if (existing != patches.end()) { in setAudioPatch()
1006 cleanUpPatch(existing->id); in setAudioPatch()
1040 if (existing == patches.end()) { in setAudioPatch()
1044 oldPatch = *existing; in setAudioPatch()
1045 *existing = *_aidl_return; in setAudioPatch()
1051 if (existing == patches.end()) { in setAudioPatch()
1054 *existing = oldPatch; in setAudioPatch()
1080 auto existing = configs.end(); in setAudioPortConfigImpl() local
[all …]
|
| /hardware/interfaces/uwb/aidl/android/hardware/uwb/fira_android/ |
| D | README.md | 8 - Andriod specific params in an existing UCI specified command/response/notification.
|
| /hardware/libhardware/tests/input/evdev/ |
| D | Android.bp | 39 // mkfifo fails on existing files.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_NV_present_barrier/ |
| D | present_barrier.adoc | 23 barrier, either to the oldest existing set of corresponding requests for
24 which there is no existing member associated with the request's swapcahin,
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/ |
| D | VK_EXT_metal_objects.adoc | 147 A `VkDeviceMemory` object can be created on an existing `MTLBuffer` object, by including
151 A `VkImage` object can be created on an existing `IOSurface` object, or one or
152 more existing Metal `MTLTexture` objects, by including those Metal objects in
156 A `VkSemaphore` or `VkEvent` object can be created on an existing `MTLSharedEvent`
|
| D | VK_KHR_dynamic_rendering.adoc | 20 . The API does not fit into most existing software architectures
113 …ynchronization info for images – synchronization is done exclusively by existing synchronization c…
117 …NT_CARE` and `VK_ATTACHMENT_STORE_OP_STORE` – other combinations in the existing API do not really…
174 …ary command buffers with dynamic rendering as they would have done in the existing render pass API.
417 This section describes issues with the existing proposal – including both open issues that you have…
429 …ar if any applications use this, it has been included to maintain compatibility with existing APIs.
|
| D | template.adoc | 18 When calling out existing API constructs or extensions, the `refpage` attribute should be used to l…
59 This section describes issues with the existing proposal – including both open issues that you have…
|
| /hardware/libhardware/modules/sensors/dynamic_sensor/ |
| D | Android.bp | 92 // 1. Use as an extension in an existing hal: declare dependency on libdynamic_sensor_ext shared
93 // library in existing sensor hal.
|
| /hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/style/ |
| D | extensions.adoc | 301 existing company or project which may wish to develop Vulkan extensions or
326 `VkVendorId` `<enums>` tag, following the existing examples.
447 existing parts of the specification to document new interactions.
448 Such changes should be inline in existing chapters.
452 introducing new return codes or extending structures to existing APIs.
462 names of existing extensions, such as `VK_KHR_surface`, for markup examples.
569 They often add an entirely new chapter, or a new section of an existing
592 ... list of existing error codes
618 * In cases where a new extension (A) modifies both core and an existing
621 extension that modified the existing extension (B) effectively becomes
[all …]
|