mirror of
https://github.com/torvalds/linux.git
synced 2024-12-11 13:41:55 +00:00
d91105e056
CAL HW interrupts are inherently racy. If we get both start and end interrupts, we don't know what has happened: did the DMA for a single frame start and end, or did one frame end and a new frame start? Usually for normal pixel frames we get the interrupts separately. If we do get both, we have to guess. The assumption in the code is that the active vertical area is larger than the blanking vertical area, and thus it is more likely that we get the end of the old frame and the start of a new frame. However, for embedded data, which is only a few lines high, we always get both interrupts. Here the assumption is that we get both for the same frame. Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl> Signed-off-by: Mauro Carvalho Chehab <mchehab@kernel.org> |
||
|---|---|---|
| .. | ||
| allegro-dvt | ||
| amlogic | ||
| amphion | ||
| aspeed | ||
| atmel | ||
| cadence | ||
| chips-media | ||
| intel | ||
| marvell | ||
| mediatek | ||
| nvidia | ||
| nxp | ||
| qcom | ||
| renesas | ||
| rockchip | ||
| samsung | ||
| st | ||
| sunxi | ||
| ti | ||
| via | ||
| xilinx | ||
| Kconfig | ||
| m2m-deinterlace.c | ||
| Makefile | ||
| video-mux.c | ||