openmax: Additional code for Buffer flag processing scheme change after EOS.
authorSeungBeom Kim <sbcrux.kim@samsung.com>
Fri, 22 Feb 2013 00:33:46 +0000 (09:33 +0900)
committerHuisung Kang <hs1218.kang@samsung.com>
Mon, 4 Mar 2013 22:52:18 +0000 (07:52 +0900)
Sometimes, OpenMAX do not use Specific output buffer.
This buffer was return from MFC after EOS.
That Buffer will be free at finish time.(It Is not a memory leak.)
But, Buffer is not used.

This patch is solved that problem.

Depends On
 - Change I5090887e: openmax: Buffer flag processing scheme change after EOS.

Change-Id: I8bcdecb8d0dc12ac985af44283412a543e219f84
Signed-off-by: SeungBeom Kim <sbcrux.kim@samsung.com>
component/video/dec/Exynos_OMX_Vdec.c
component/video/enc/Exynos_OMX_Venc.c

index 7b7dcb4cee247310c04efa85c51aa8c5805dc0b5..1b3948872a2e98fb16426b5b5af15cca7c7e5a93 100644 (file)
@@ -676,6 +676,8 @@ OMX_BOOL Exynos_Postprocess_OutputData(OMX_COMPONENTTYPE *pOMXComponent, EXYNOS_
                 ((outputUseBuffer->nFlags & OMX_BUFFERFLAG_EOS) == OMX_BUFFERFLAG_EOS) ||
                 (CHECK_PORT_BEING_FLUSHED(exynosOutputPort)))
                 Exynos_OutputBufferReturn(pOMXComponent, outputUseBuffer);
+            else
+                Exynos_OMX_FillThisBuffer(pOMXComponent, outputUseBuffer->bufferHeader);
         }
     } else {
         ret = OMX_FALSE;
index 01ecccf1ffe76715a8d4b0ce80726feb39121cf8..bd748e6f7fc5f361e363a4f420721f74d1d1c9a1 100644 (file)
@@ -669,6 +669,8 @@ OMX_BOOL Exynos_Postprocess_OutputData(OMX_COMPONENTTYPE *pOMXComponent, EXYNOS_
                 ((outputUseBuffer->nFlags & OMX_BUFFERFLAG_EOS) == OMX_BUFFERFLAG_EOS) ||
                 (CHECK_PORT_BEING_FLUSHED(exynosOutputPort)))
                 Exynos_OutputBufferReturn(pOMXComponent, outputUseBuffer);
+            else
+                Exynos_OMX_FillThisBuffer(pOMXComponent, outputUseBuffer->bufferHeader);
         }
     } else {
         ret = OMX_FALSE;