Home
last modified time | relevance | path

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

/hardware/qcom/camera/msm8998/QCamera2/HAL3/test/
DQCameraHAL3MainTestContext.cpp66 int choice; in hal3appGetUserEvent() local
81 choice = hal3appDisplaySensorMenu(num_of_cameras); in hal3appGetUserEvent()
82 if (choice >= num_of_cameras || choice < 0) { in hal3appGetUserEvent()
87 mCamHal3Base->mCameraIndex = choice; in hal3appGetUserEvent()
88 rc = mCamHal3Base->hal3appCameraLibOpen(choice); in hal3appGetUserEvent()
92 choice = hal3appPrintMenu(); in hal3appGetUserEvent()
93 switch(choice) { in hal3appGetUserEvent()
182 }while(choice != MENU_EXIT); in hal3appGetUserEvent()
189 int i, choice; in hal3appDisplaySensorMenu() local
204 fscanf(stdin, "%d", &choice); in hal3appDisplaySensorMenu()
[all …]
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/
DVK_EXT_opacity_micromap.adoc23 The mapping of the data onto the mesh is one design choice. Traditionally, texturing onto geometry …
30 Relatedly, the mapping from triangle to index is another design choice. With raster images, pitch o…
DVK_EXT_shader_tile_image.adoc60 This proposal targets the first choice.
69 The reasoning behind this choice is that:
446 This design choice is in-line with other API extensions (GL framebuffer fetch and framebuffer fetch…
457 Given the design choice made for issue 8, the alternate options do not add any value.
DVK_EXT_shader_object.adoc28 …, renderers with a choice of API have largely chosen to avoid Vulkan and its "pipelined" contempor…
DVK_KHR_fragment_shading_rate.adoc323 …ng of the final combiner operation as an addition of log2 values, so the choice was made to descri…
DVK_ANDROID_external_format_resolve.adoc309 All of this is a deliberate choice due to time constraints.
DVK_EXT_graphics_pipeline_library.adoc61 However, it takes the choice of fast-linking vs. whole program optimization
/hardware/interfaces/bluetooth/1.1/
DIBluetoothHci.hal26 * controller chip. This boundary is the natural choice for a Hardware
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/images/
DREADME.adoc8 color palette (white, black, 50% gray and pure red), one choice of dotted
/hardware/interfaces/bluetooth/1.0/
DIBluetoothHci.hal24 * controller chip. This boundary is the natural choice for a Hardware
/hardware/interfaces/security/rkp/
DREADME.md114 widely-used and widely-implemented to make it a practical choice.
124 choice for algorithm implies the implementor should also choose the P256 public
/hardware/interfaces/broadcastradio/1.1/
DITuner.hal126 * this option. This is purely user choice, ie. does not reflect digital-
/hardware/libhardware/modules/camera/3_4/
DREADME.md142 stack's choice ("implementation defined"). Very few cameras actually support
/hardware/interfaces/broadcastradio/2.0/
Dtypes.hal59 * this option. This is purely user choice, ie. does not reflect digital-
72 * user choice, it does not reflect the actual state of handover.
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/appendices/
DVK_NV_device_generated_commands.adoc117 This is a different design choice compared to the serial command stream
DVK_EXT_image_drm_format_modifier.adoc180 In this case, the application should defer the choice of the image's
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/style/
Dmarkup.adoc1136 | runtime | run time / run-time | Arbitrary choice for consistency
1218 allowed, each choice still must have well-defined behavior.
1227 | And all other such terms of choice. Use _may{cl}_ or _can{cl}_
/hardware/interfaces/graphics/common/1.0/
Dtypes.hal157 * A format indicating that the choice of format is entirely up to the
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/
Dqueries.adoc1888 choice of one of the following behaviors:
2020 choice of one of the following behaviors:
Ddevsandqueues.adoc171 Otherwise, the choice of what values to return may: be dictated by operating
Dmemory.adoc4239 If a given choice of image parameters are supported for import, they can:
Dresources.adoc2729 The choice of modifier is implementation-dependent.
2997 The choice of "`bits per component`" terminology was chosen so that the same
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/
Dregistry.adoc75 This choice is based on prior experience with the SGI `.spec` file format
DChangeLog.adoc996 * Fix style guide word choice table markup problem that resulted in
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/katex/
Dkatex.mjs16740 // another natural choice (the user requested math mode), but