aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorBuddy Liong2016-06-22 12:13:08 -0500
committerBuddy Liong2016-06-22 12:13:08 -0500
commitf83e785d2b98404fed9e3a6264bf4945c65abd12 (patch)
tree8552d5db0e5608f518ff0d231d794a8615bc471f /libdce_android.c
parentd0d2e63691f4c6906aa9ae28c16f5b92de8c1bcd (diff)
downloadhardware-ti-libdce-f83e785d2b98404fed9e3a6264bf4945c65abd12.tar.gz
hardware-ti-libdce-f83e785d2b98404fed9e3a6264bf4945c65abd12.tar.xz
hardware-ti-libdce-f83e785d2b98404fed9e3a6264bf4945c65abd12.zip
Valid id checking for callbackmsg[id]).row_mode in process()
In VIDDEC3_process or VIDENC2_process, if low latency is used, then id will have a valid value of >= 0. When full frame is used, after process call, there is a condition check of callbackmsg[id]).row_mode. Problem is that id might not be valid for full frame. With id value < 0, the value in callbackmsg[id]).row_mode can be guarantee to be correct. Issue is found when id = -1 and the value of callbackmsg[-1]).row_mode points to less than 0, which causes the condition to pass. This commit is fixing the issue by adding additional check to make sure id is >= 0 when calling callbackmsg[id]).row_mode so that the condition check will be valid to determine low latency mode or full frame mode after process(). Change-Id: I93209e4da42305e807824565bf676c8bdd33d72a Signed-off-by: Buddy Liong <buddy.liong@ti.com>
Diffstat (limited to 'libdce_android.c')
0 files changed, 0 insertions, 0 deletions