tag 846bf16df89c2f05bb04925ccc43935578744af7
tagger The Android Open Source Project <initial-contribution@android.com> Mon Aug 05 10:52:28 2019 -0700
object 41db963edef0129a5d5dcda319e9946779b3985d

Android 9.0.0 Release 47 (PQ3B.190801.002)

commit 41db963edef0129a5d5dcda319e9946779b3985d
author Pin-chih Lin <johnylin@google.com> Tue Sep 11 15:41:39 2018 +0800
committer Pin-chih Lin <johnylin@google.com> Wed Sep 12 11:29:18 2018 +0800
tree 7f1842dbe7fb43022e4fd61eec44dd1ee045e5a8
parent 3fe0c8d0909e8b3429e187c1de88c90a635f07ea

C2VDAComponent: do not rely on monotonic increasing output timestamp

Unfortuneately the previous assumption of getting monotonic increasing
timestamp as display order of output buffers is not always right. In
testH264_adaptiveSkipBack, the timestamp goes back and forth.

For such cases we cannot rely on timestamp for checking work done anymore, we
cannot help but rely on input flags for recognizing CSD buffer works, which
doesn't have a correlated output buffer; otherwise, work is done only if both
input and output buffer are returned from VDA.

Bug: 80402878
Test: android.media.cts.AdaptivePlaybackTest#testH264_adaptiveSkipBack for
codec2.0 on eve-arcnext

Change-Id: Ib3af3ca0ee90925187662af4ae0eb4d628ad21a6