| author | Pratyush Yadav <p.yadav@ti.com> | |
| Thu, 18 Feb 2021 12:09:41 +0000 (17:39 +0530) | ||
| committer | Vignesh Raghavendra <vigneshr@ti.com> | |
| Thu, 18 Feb 2021 12:36:26 +0000 (18:06 +0530) | ||
| commit | 3abf65738c67f85c2cecec403bb65e2ba5043304 | |
| tree | ab28e0ff4451f071a33f24dff015eb4748e54327 | tree | snapshot (tar.xz tar.gz zip) |
| parent | 86688e9f8a2e6912a005d9201ff28a2273669fab | commit | diff |
HACK: media: ti-vpe: csi2rx: Drain DMA when stopping stream
Some data might be stuck in the DMA pipeline because the application
does not tell us how many frames it wants to capture. So there will
always be some time delay between the application requesting the last
frame it needs and stopping the stream which will stop DMA. Drain that
data so it does not corrupt the next frame captured when the stream is
re-started later.
Marking this as a hack for now because it is not clear yet whether this
is a hardware problem or a software problem. If it does turn out to be a
hardware problem, it can be presented as a workaround instead.
Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
Some data might be stuck in the DMA pipeline because the application
does not tell us how many frames it wants to capture. So there will
always be some time delay between the application requesting the last
frame it needs and stopping the stream which will stop DMA. Drain that
data so it does not corrupt the next frame captured when the stream is
re-started later.
Marking this as a hack for now because it is not clear yet whether this
is a hardware problem or a software problem. If it does turn out to be a
hardware problem, it can be presented as a workaround instead.
Signed-off-by: Pratyush Yadav <p.yadav@ti.com>
Signed-off-by: Vignesh Raghavendra <vigneshr@ti.com>
| drivers/media/platform/ti-vpe/ti-csi2rx.c | diff | blob | history |