Re: [PATCH] media: coda: fix comparision of decoded frames' indexes

2017-11-23 Thread Martin Kepplinger
Am 22.11.2017 14:43 schrieb Philipp Zabel: Hi Martin, On Fri, 2017-11-17 at 15:30 +0100, Martin Kepplinger wrote: At this point the driver looks the currently decoded frame's index and compares is to VPU-specific state values. Directly before this if and else statements the indexes are read

Re: [PATCH] media: coda: fix comparision of decoded frames' indexes

2017-11-23 Thread Martin Kepplinger
Am 22.11.2017 14:43 schrieb Philipp Zabel: Hi Martin, On Fri, 2017-11-17 at 15:30 +0100, Martin Kepplinger wrote: At this point the driver looks the currently decoded frame's index and compares is to VPU-specific state values. Directly before this if and else statements the indexes are read

Re: [PATCH] media: coda: fix comparision of decoded frames' indexes

2017-11-22 Thread Philipp Zabel
Hi Martin, On Fri, 2017-11-17 at 15:30 +0100, Martin Kepplinger wrote: > At this point the driver looks the currently decoded frame's index > and compares is to VPU-specific state values. Directly before this > if and else statements the indexes are read (index for decoded and > for displayed

Re: [PATCH] media: coda: fix comparision of decoded frames' indexes

2017-11-22 Thread Philipp Zabel
Hi Martin, On Fri, 2017-11-17 at 15:30 +0100, Martin Kepplinger wrote: > At this point the driver looks the currently decoded frame's index > and compares is to VPU-specific state values. Directly before this > if and else statements the indexes are read (index for decoded and > for displayed

[PATCH] media: coda: fix comparision of decoded frames' indexes

2017-11-17 Thread Martin Kepplinger
At this point the driver looks the currently decoded frame's index and compares is to VPU-specific state values. Directly before this if and else statements the indexes are read (index for decoded and for displayed frame). Now what is saved in ctx->display_idx is an older value at this point!

[PATCH] media: coda: fix comparision of decoded frames' indexes

2017-11-17 Thread Martin Kepplinger
At this point the driver looks the currently decoded frame's index and compares is to VPU-specific state values. Directly before this if and else statements the indexes are read (index for decoded and for displayed frame). Now what is saved in ctx->display_idx is an older value at this point!