On 9/26/24 1:16 PM, Philipp Zabel wrote:
On Mi, 2024-09-25 at 22:45 +0200, Marek Vasut wrote:
[...]
The driver is not taking ownership of prev_buf, only curr_buf is guaranteed to
exist until v4l2_m2m_job_finish() is called. Usespace could streamoff, allocate
new buffers, and then an old freed buffer may endup being used.
So, what should I do about this ? Is there some way to ref the buffer to
keep it around ?
Have a look how other deinterlacers with temporal filtering do it.
sunxi/sun8i-di or ti/vpe look like candidates.
I don't see exactly what those drivers are doing differently to protect
the prev buffer during deinterlacing . Can you be more specific ?
