summaryrefslogtreecommitdiffstats
path: root/Documentation/powerpc
diff options
context:
space:
mode:
authorTomi Valkeinen <tomi.valkeinen@ideasonboard.com>2022-04-26 09:06:18 +0200
committerMauro Carvalho Chehab <mchehab@kernel.org>2022-08-30 14:27:05 +0200
commitd91105e0567dabf487f81019e8b609706334d5ed (patch)
treed06893fa44abc03bb213b9d7583751724bebc774 /Documentation/powerpc
parent0872dc04cf65fdfaa1d67453d535f8181982848b (diff)
downloadlinux-d91105e0567dabf487f81019e8b609706334d5ed.tar.bz2
media: ti: cal: fix wdma irq for metadata
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>
Diffstat (limited to 'Documentation/powerpc')
0 files changed, 0 insertions, 0 deletions