Home
last modified time | relevance | path

Searched refs:Passthrough (Results 1 – 9 of 9) sorted by relevance

/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/
DVK_NV_geometry_shader_passthrough.adoc55 <<geometry-passthrough,Geometry Shader Passthrough>>
86 Passthrough Interface Matching>>.
Dglossary.adoc1236 Passthrough Geometry Shader::
/hardware/google/gfxstream/host/vulkan/
DVkEmulatedPhysicalDeviceMemoryTests.cpp81 TEST(VkGuestMemoryUtilsTest, Passthrough) { in TEST() argument
/hardware/interfaces/health/2.1/
DIHealth.hal42 * Passthrough implementations are not required to send health info to all
/hardware/interfaces/renderscript/1.0/
Dtypes.hal30 // running in Passthrough mode.
DIContext.hal188 * HIDL is always running in Passthrough mode for RenderScript, so the
313 * HIDL is always running in Passthrough mode for RenderScript, so the
331 * HIDL is always running in Passthrough mode for RenderScript, so the
348 * HIDL is always running in Passthrough mode for RenderScript, so the
373 * HIDL is always running in Passthrough mode for RenderScript, so the
402 * HIDL is always running in Passthrough mode for RenderScript, so the
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/
Dgeometry.adoc140 == Geometry Shader Passthrough
190 === Passthrough Interface Matching argument
Dinterfaces.adoc24 * <<geometry-passthrough-passthrough,Geometry Shader Passthrough>>
186 are described in the <<geometry-passthrough-interface,Passthrough Interface
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/style/
Dmarkup.adoc210 | Passthrough | `pass:[++++]` | For some kinds of <<writing-math,math markup>>