On Wednesday, February 09, 2011 07:23:49 Subash Patel wrote:
In the reference architecture in ppt, we can directly wait for the RSZ interrupt, if we configure the hardware pipe. It was my mis-understanding as each of those hardware blocks can deliver interrupts too. In that way ARM needs to just work at finished frame, like forward it to the display or codec engine etc. V4L2 can be easily used for such hardware architecture.
What hardware are you developing for anyway? If it is Samsung hardware, then you should be aware that Samsung Poland is doing a lot of work in V4L2 to add support to the s5p SoC series.
But if a ISP chooses to do the above work in a seperate (dsp)processor, can we still use V4L2? OMX seems better in such environment. Let me know if there is any other alternative.
In general such systems are either implemented with custom APIs or OMX (my guess is that in the OMX case it probably uses the same custom API internally, but that's just a guess).
There is however nothing that prevents V4L2 from being used instead: it really doesn't matter from the point of view of V4L2 whether the V4L driver sets hardware registers or makes mailbox calls to a separate DSP/CPU.
It hasn't been done yet since the V4L2 has only recently matured enough to support such systems, and because of the often closed-source nature of such systems.
Regards,
Hans