Home
last modified time | relevance | path

Searched refs:ownership (Results 1 – 25 of 116) sorted by relevance

12345

/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/commonvalidity/
Dimage_memory_barrier_common.adoc9 <<synchronization-queue-transfers, queue family ownership transfer>> or
17 <<synchronization-queue-transfers, queue family ownership transfer>> or
26 <<synchronization-queue-transfers, queue family ownership transfer>> or
35 <<synchronization-queue-transfers, queue family ownership transfer>> or
44 <<synchronization-queue-transfers, queue family ownership transfer>> or
52 <<synchronization-queue-transfers, queue family ownership transfer>> or
60 <<synchronization-queue-transfers, queue family ownership transfer>> or
67 <<synchronization-queue-transfers, queue family ownership transfer>> or
75 <<synchronization-queue-transfers, queue family ownership transfer>> or
84 <<synchronization-queue-transfers, queue family ownership transfer>> or
[all …]
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/
DVK_EXT_external_memory_acquire_unmodified.adoc11 cost of memory barriers that acquire ownership of a resource from an external
17 A memory barrier that acquires ownership of a resource from an external queue
59 When an application releases ownership of a resource to an external queue
60 family and later re-acquires ownership, the external queue family may have
61 modified the resource's external memory during its ownership.
63 then, when the application re-acquires ownership, the Vulkan implementation
64 must, during the ownership-acquire operation, synchronize the resource's non-external
77 ownership of the image to
105 application's most recent release of ownership to the external queue family
106 until the application's current ownership acquire operation.
[all …]
/hardware/google/aemu/base/
DStdioStream.cpp23 StdioStream::StdioStream(FILE* file, Ownership ownership) : in StdioStream() argument
24 mFile(file), mOwnership(ownership) {} in StdioStream()
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/
DVK_EXT_external_memory_acquire_unmodified.adoc19 A memory barrier may: have a performance penalty when acquiring ownership of
22 ownership of the subresource range was previously released to the external
DVK_KHR_external_semaphore_fd.adoc35 A successful get call transfers ownership of the file descriptor to the
DVK_FUCHSIA_external_semaphore.adoc34 A successful get call transfers ownership of the Zircon event handle to the
DVK_EXT_queue_family_foreign.adoc24 ename:VK_QUEUE_FAMILY_FOREIGN_EXT, which can be used to transfer ownership
DVK_KHR_shared_presentable_image.adoc104 10) Can the ownership of a shared presentable image be transferred to a
108 It is not possible to transfer ownership of a shared presentable image
DVK_KHR_external_memory_fd.adoc36 A successful get call transfers ownership of the file descriptor to the
DVK_NV_external_memory_win32.adoc69 A successful get call transfers ownership of the handle to the application,
70 while an import transfers ownership to the associated driver.
DVK_KHR_external_memory_win32.adoc48 A successful get call transfers ownership of the handle to the application.
DVK_KHR_external_semaphore_win32.adoc35 A successful get call transfers ownership of the handle to the application.
DVK_ANDROID_external_memory_android_hardware_buffer.adoc99 gives a raw view of the memory contents, and does not involve ownership.
106 view of the data and does not imply ownership (this means implementations
/hardware/google/aemu/base/include/aemu/base/files/
DStdioStream.h32 StdioStream(FILE* file = nullptr, Ownership ownership = kNotOwner);
/hardware/interfaces/media/bufferpool/1.0/
Dtypes.hal44 * Buffer ownership status for the specified client.
71 * Buffer ownership status change message. This message is
DREADME.md12 process. FMQ is used to send buffer ownership change status from a client
18 FMQ is used to send buffer ownership status changes to a buffer pool from a
DIAccessor.hal32 * FMQ is used to send buffer ownership status changes to a buffer pool
/hardware/interfaces/media/bufferpool/2.0/
DREADME.md12 process. FMQ is used to send buffer ownership change status from a client
18 FMQ is used to send buffer ownership status changes to a buffer pool from a
Dtypes.hal44 * Buffer ownership status for the specified client.
73 * Buffer ownership status change message. This message is
/hardware/google/gfxstream/guest/mesa/src/vulkan/wsi/
Dwsi_common.h213 VkBool32 ownership);
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_FUCHSIA_external_memory/
Ddevice_memory.adoc21 Importing VMO handles to the Vulkan instance transfers ownership of the
114 Similar to importing, exporting a VMO handle from Vulkan transfers ownership
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_EXT_acquire_xlib_display/
Dacquire_xlib_display.adoc33 ownership of its virtual terminal.
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/
Dsynchronization.adoc2143 To avoid leaking resources, the application must: release ownership of them
2219 transfer ownership of it to the application.
2220 To avoid leaking resources, the application must: release ownership of the
2228 or transfer ownership back to Vulkan by using the file descriptor to import
2450 stext:NvSciSyncFence handle and transfer the ownership of the
2452 To avoid leaking resources, the application must: release of the ownership
2485 stext:NvSciSyncObj handle and transfer the ownership of the
2487 To avoid leaking resources, the application must: release of the ownership
2929 Importing a fence payload from Windows handles does not transfer ownership
2932 ownership using the code:CloseHandle system call when the handle is no
[all …]
/hardware/interfaces/automotive/evs/1.0/
DIEvsEnumerator.hal87 * without acquiring exclusive ownership of the display.
/hardware/interfaces/media/omx/1.0/
DIOmxNode.hal272 * ownership of the fence even if this call fails.
296 * ownership of the fence even if this call fails.

12345