Home
last modified time | relevance | path

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

12

/hardware/google/gfxstream/guest/android-emu/aemu/base/
Dring_buffer.c82 struct ring_buffer* r, const void* data, uint32_t step_size, uint32_t steps) { in ring_buffer_write() argument
86 for (i = 0; i < steps; ++i) { in ring_buffer_write()
117 return (long)steps; in ring_buffer_write()
121 struct ring_buffer* r, void* data, uint32_t step_size, uint32_t steps) { in ring_buffer_read() argument
125 for (i = 0; i < steps; ++i) { in ring_buffer_read()
156 return (long)steps; in ring_buffer_read()
160 struct ring_buffer* r, uint32_t step_size, uint32_t steps) { in ring_buffer_advance_write() argument
163 for (i = 0; i < steps; ++i) { in ring_buffer_advance_write()
173 return (long)steps; in ring_buffer_advance_write()
177 struct ring_buffer* r, uint32_t step_size, uint32_t steps) { in ring_buffer_advance_read() argument
[all …]
Dring_buffer.h52 struct ring_buffer* r, const void* data, uint32_t step_size, uint32_t steps);
54 struct ring_buffer* r, void* data, uint32_t step_size, uint32_t steps);
59 struct ring_buffer* r, uint32_t step_size, uint32_t steps);
61 struct ring_buffer* r, uint32_t step_size, uint32_t steps);
103 const void* data, uint32_t step_size, uint32_t steps);
107 void* data, uint32_t step_size, uint32_t steps);
/hardware/google/aemu/base/include/aemu/base/
Dring_buffer.h52 struct ring_buffer* r, const void* data, uint32_t step_size, uint32_t steps);
54 struct ring_buffer* r, void* data, uint32_t step_size, uint32_t steps);
59 struct ring_buffer* r, uint32_t step_size, uint32_t steps);
61 struct ring_buffer* r, uint32_t step_size, uint32_t steps);
103 const void* data, uint32_t step_size, uint32_t steps);
107 void* data, uint32_t step_size, uint32_t steps);
/hardware/google/aemu/base/
Dring_buffer.cpp68 struct ring_buffer* r, const void* data, uint32_t step_size, uint32_t steps) { in ring_buffer_write() argument
72 for (i = 0; i < steps; ++i) { in ring_buffer_write()
103 return (long)steps; in ring_buffer_write()
107 struct ring_buffer* r, void* data, uint32_t step_size, uint32_t steps) { in ring_buffer_read() argument
111 for (i = 0; i < steps; ++i) { in ring_buffer_read()
142 return (long)steps; in ring_buffer_read()
146 struct ring_buffer* r, uint32_t step_size, uint32_t steps) { in ring_buffer_advance_write() argument
149 for (i = 0; i < steps; ++i) { in ring_buffer_advance_write()
159 return (long)steps; in ring_buffer_advance_write()
163 struct ring_buffer* r, uint32_t step_size, uint32_t steps) { in ring_buffer_advance_read() argument
[all …]
/hardware/interfaces/automotive/vehicle/2.0/default/tests/fuzzer/
DREADME.md30 This describes steps to build vehicleManager_fuzzer binary.
46 ##### Some Additional steps needed to run the vehicleManager_fuzzer successfully on device
/hardware/interfaces/vibrator/1.0/
DIVibrator.hal50 * have exactly 255 steps, it must do it's best to map it
51 * onto the number of steps it does have.
/hardware/interfaces/biometrics/fingerprint/2.1/
DIBiometricsFingerprintClientCallback.hal28 * @param remaining the number of remaining steps before enrolllment is complete
73 * @param remaining the number of remaining steps before enumeration is complete
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_NV_device_generated_commands/
Dgeneratedcommands.adoc9 device, for which these principle steps are to be taken:
/hardware/interfaces/bluetooth/1.0/default/test/fuzzer/
DREADME.md30 This describes steps to build bluetoothV1.0_fuzzer binary.
/hardware/interfaces/keymaster/4.0/support/fuzzer/
DREADME.md36 This describes steps to build keymaster4_attestation_fuzzer, keymaster4_authSet_fuzzer and keymaste…
/hardware/interfaces/drm/1.4/
Dtypes.hal121 * Required steps where not performed before provisioning was attempted.
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/proposals/
DVK_EXT_external_memory_acquire_unmodified.adoc187 Solution (A) works well for steps (i, j, k) because the presentation engine is
194 Solution (D) works well for all steps in the sequence. In particular, between
247 allows the application to query, between steps (f) and (g), whether the library
DVK_KHR_fragment_shading_rate.adoc23 …ng occurs, but this is always applied uniformly across the screen; though steps can be taken to ap…
/hardware/interfaces/wifi/1.4/
Dtypes.hal516 * Average rssi in 0.5 dB steps e.g. 143 implies -71.5 dB.
521 * Rssi spread in 0.5 dB steps e.g. 5 implies 2.5 dB spread (optional).
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/
Dfragmentdensitymapops.adoc129 The texels follow the standard conversion steps up to and including
Dtextures.adoc122 image operations, and <<textures-normalized-operations,certain steps>> are
391 _Texel input operations_ are a set of steps that are performed on state,
394 They include the following steps, which are performed in the listed order:
414 gathering), these steps are applied for each texel that is used in the
416 Depending on the type of image instruction, other steps are conditionally
417 performed between these steps or involving multiple coordinate or texel
690 cube map face (as described in the prior section), the following steps are
1527 _Texel output operations_ are a set of steps that are performed on state,
1530 They include the following steps, which are performed in the listed order:
4108 steps described in this chapter are performed as if for
Dvideo_decode_h264_extensions.adoc20 This process is performed according to the <<decode-operation-steps,video
21 decode operation steps>> with the codec-specific semantics defined in
Dvideo_decode_h265_extensions.adoc20 This process is performed according to the <<decode-operation-steps,video
21 decode operation steps>> with the codec-specific semantics defined in
Dvideo_decode_extensions.adoc104 [[decode-operation-steps]]
107 Each video decode operation performs the following steps in the
/hardware/interfaces/biometrics/face/1.0/
DIBiometricsFaceClientCallback.hal32 * @param remaining The number of remaining steps before enrolllment is
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/
DBUILD.adoc19 It documents how to set up your build environment, build steps and targets,
440 Linux) distribution by executing the same steps as the
444 It should be possible to apply the same steps in a Windows Subsystem for
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/xml/
DREADME.adoc124 steps will build the Vulkan headers and test that `vulkan_core.h` compiles:
/hardware/google/gfxstream/codegen/vulkan/vulkan-docs-next/chapters/VK_NV_cuda_kernel_launch/
Dmodule.adoc192 A typical use of vkGetCudaModuleCacheNV happens in two steps:
/hardware/interfaces/wifi/1.6/
Dtypes.hal502 * Average rssi in 0.5 dB steps e.g. 143 implies -71.5 dB.
507 * Rssi spread in 0.5 dB steps e.g. 5 implies 2.5 dB spread (optional).
/hardware/interfaces/wifi/1.0/
Dtypes.hal1840 * Average rssi in 0.5 dB steps e.g. 143 implies -71.5 dB.
1844 * Rssi spread in 0.5 dB steps e.g. 5 implies 2.5 dB spread (optional).

12