Commit 83f31c8a authored by Lucas Stach's avatar Lucas Stach Committed by Mauro Carvalho Chehab

[media] coda: adjust sequence offset after unexpected decoded frame

If userspace doesn't properly separate the bitstream input into
individual frames (which may happen for example on slightly
corrupted streams) the CODA hardware may decode more frames
than we expect. We already log an error in this case, but it's
also necessary to adjust the sequence offset. Otherwise we
spam the log with a sequence number mismatch on every frame
frame after the unexpected one.
Signed-off-by: default avatarLucas Stach <l.stach@pengutronix.de>
Signed-off-by: default avatarKamil Debski <k.debski@samsung.com>
Signed-off-by: default avatarMauro Carvalho Chehab <mchehab@osg.samsung.com>
parent 07ba277f
...@@ -1822,6 +1822,7 @@ static void coda_finish_decode(struct coda_ctx *ctx) ...@@ -1822,6 +1822,7 @@ static void coda_finish_decode(struct coda_ctx *ctx)
memset(&ctx->frame_metas[decoded_idx], 0, memset(&ctx->frame_metas[decoded_idx], 0,
sizeof(struct coda_buffer_meta)); sizeof(struct coda_buffer_meta));
ctx->frame_metas[decoded_idx].sequence = val; ctx->frame_metas[decoded_idx].sequence = val;
ctx->sequence_offset++;
} }
mutex_unlock(&ctx->bitstream_mutex); mutex_unlock(&ctx->bitstream_mutex);
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment