summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorPhilipp Zabel <p.zabel@pengutronix.de>2012-07-25 15:46:09 +0200
committerMauro Carvalho Chehab <mchehab@redhat.com>2012-09-26 21:35:54 +0200
commitbcedb4c2422801e37c3d9c716597e8883d1b4e87 (patch)
tree3cfc89dccf606be4b2fb051eea83e0e2cd5b94e9 /drivers
parent[media] media: coda: allocate internal framebuffers separately from v4l2 buffers (diff)
downloadlinux-bcedb4c2422801e37c3d9c716597e8883d1b4e87.tar.xz
linux-bcedb4c2422801e37c3d9c716597e8883d1b4e87.zip
[media] media: coda: ignore coda busy status in coda_job_ready
job_ready is supposed to signal whether a context is ready to be added to the job queue, not whether the CODA is ready to run it immediately. Calling v4l2_m2m_job_finish at the end of coda_irq_handler already guarantees that the coda is ready when v4l2-mem2mem eventually tries to run the next queued job. Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> Tested-by: Javier Martin <javier.martin@vista-silicon.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/media/platform/coda.c6
1 files changed, 0 insertions, 6 deletions
diff --git a/drivers/media/platform/coda.c b/drivers/media/platform/coda.c
index 9223693b9a8d..01a8fe3e17f9 100644
--- a/drivers/media/platform/coda.c
+++ b/drivers/media/platform/coda.c
@@ -743,12 +743,6 @@ static int coda_job_ready(void *m2m_priv)
return 0;
}
- if (coda_isbusy(ctx->dev)) {
- v4l2_dbg(1, coda_debug, &ctx->dev->v4l2_dev,
- "not ready: coda is still busy.\n");
- return 0;
- }
-
v4l2_dbg(1, coda_debug, &ctx->dev->v4l2_dev,
"job ready\n");
return 1;