Searched refs:flush (Results 1 - 25 of 145) sorted by relevance

123456

/hardware/libhardware/modules/sensors/dynamic_sensor/
H A DBaseSensorObject.cpp42 int BaseSensorObject::flush() { function in class:android::SensorHalExt::BaseSensorObject
H A DBaseSensorObject.h53 // flush sensor, default implementation will send a flush complete event back.
54 virtual int flush();
H A Dsensors.cpp42 device.flush = FlushWrapper;
75 int SensorContext::flush(int handle) { function in class:SensorContext
76 return mDynamicSensorManager->flush(handle);
116 return reinterpret_cast<SensorContext *>(dev)->flush(handle);
H A Dsensors.h55 int flush(int handle);
/hardware/intel/common/libmix/videoencoder/
H A DVideoEncoderInterface.h27 virtual void flush(void) = 0;
H A DPVSoftMPEG4Encoder.h38 virtual void flush(void) { } function in class:PVSoftMPEG4Encoder
/hardware/interfaces/camera/device/3.2/
H A DICameraDeviceSession.hal284 * flush:
291 * held at the time of flush() (whether successfully filled or not) may be
301 * flush() may be called concurrently to processCaptureRequest(), with the
306 * be started after flush has been invoked but has not returned yet. If such
307 * a call happens before flush() returns, the HAL must treat the new
364 * 4. If a flush() is invoked while a processCaptureRequest() invocation
366 * addition, if a processCaptureRequest() call is made after flush()
367 * has been invoked but before flush() has returned, the capture request
371 * flush() must only return when there are no more outstanding buffers or
377 * the partial failure cases as well, as it could help improve the flush
[all...]
/hardware/interfaces/gnss/1.0/
H A DIGnssBatching.hal123 * no locations to flush (in which case the Location vector must be empty).
128 flush();
/hardware/intel/common/libmix/videodecoder/
H A DVideoDecoderInterface.h29 virtual void flush() = 0;
H A DVideoDecoderMPEG2.h34 virtual void flush(void);
H A DVideoDecoderMPEG4.h30 virtual void flush(void);
H A DVideoDecoderVP8.h30 virtual void flush(void);
H A DVideoDecoderWMV.h30 virtual void flush(void);
/hardware/intel/img/hwcomposer/merrifield/ips/tangier/
H A DTngOverlayPlane.h45 virtual bool flush(uint32_t flags);
/hardware/qcom/camera/msm8998/QCamera2/util/
H A DQCameraQueue.h55 void flush();
/hardware/qcom/media/msm8974/mm-video-legacy/vidc/vdec/inc/
H A Dframeparser.h76 void flush ();
/hardware/qcom/media/msm8974/mm-video-v4l2/vidc/vdec/inc/
H A Dframeparser.h77 void flush ();
/hardware/qcom/media/msm8996/mm-video-v4l2/vidc/vdec/inc/
H A Dframeparser.h78 void flush ();
/hardware/qcom/media/msm8998/mm-video-v4l2/vidc/vdec/inc/
H A Dframeparser.h78 void flush ();
/hardware/interfaces/sensors/1.0/
H A DISensors.hal101 * Trigger a flush of internal FIFO.
108 * is a one-shot sensor, flush must return BAD_VALUE and not generate any
109 * flush complete metadata. If the sensor is not active at the time flush()
110 * is called, flush() return BAD_VALUE.
115 flush(int32_t sensorHandle) generates (Result result);
/hardware/interfaces/automotive/vehicle/2.0/default/common/include/vhal_v2_0/
H A DConcurrentQueue.h38 std::vector<T> flush() { function in class:android::ConcurrentQueue
135 std::vector<T> items = mQueue->flush();
/hardware/intel/img/hwcomposer/merrifield/ips/anniedale/
H A DAnnOverlayPlane.h57 virtual bool flush(uint32_t flags);
/hardware/intel/img/hwcomposer/moorefield_hdmi/ips/anniedale/
H A DAnnOverlayPlane.h57 virtual bool flush(uint32_t flags);
/hardware/libhardware/include/hardware/
H A Dactivity_recognition.h79 * A flush_complete event which indicates that a flush() has been successfully completed. This
82 * reported to the framework. An event of this type should be generated only if flush() has been
83 * explicitly called and if the FIFO is empty at the time flush() is called it should trivially
86 * A flush complete event should have the following parameters set.
91 * See (*flush)() for more details.
112 * is a flush complete event, this should be set to zero.
225 int (*flush)(const struct activity_recognition_device* dev); member in struct:activity_recognition_device
/hardware/interfaces/media/omx/1.0/vts/functional/
H A DREADME.md12 This folder includes test fixtures that tests aspects common to all omx compatible components. For instance, port enabling/disabling, enumerating port formats, state transitions, flush, ..., stay common to all components irrespective of the service they offer. Test fixtures here are directed towards testing these (omx core). Every standard OMX compatible component is expected to pass these tests.
17 This folder includes test fixtures associated with testing audio encoder and decoder components such as simple encoding of a raw clip or decoding of an elementary stream, end of stream test, timestamp deviations test, flush test and so on. These tests are aimed towards testing the plugin that connects the component to the omx core.
26 This folder includes test fixtures associated with testing video encoder and decoder components such as simple encoding of a raw clip or decoding of an elementary stream, end of stream test, timestamp deviations test, flush test and so on. These tests are aimed towards testing the plugin that connects the component to the omx core.

Completed in 2212 milliseconds

123456