This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[DM3730] OMAP 3 ISP Resizer

Other Parts Discussed in Thread: OMAP3530

Hi

I am using the media-ctl framework and would like to do the resizing. Previously, using the Resizer code from TI works perfectly on dvsdk4.02 where it looks for /dev/omap-resizer and does the resizing on the evaluation board. But I'm using the OMAP3 ISP resizer, I changed the /dev/omap-resizer to take in /dev/video5. It didnt work as expected. Is there some workaround or any solutions?

Would fwrite into /dev/video5 and fread from /dev/video6 works?

Please help. Thanks.

- entity 10: OMAP3 ISP resizer (2 pads, 4 links)
type V4L2 subdev subtype Unknown
device node name /dev/v4l-subdev4
pad0: sink [fmt: UYVY2X8/720x480 crop.bounds:(0,0) crop:(0,0)/720x480]
<- 'OMAP3 ISP CCDC':1 []
<- 'OMAP3 ISP preview':1 []
<- 'OMAP3 ISP resizer input':0 [ENABLED]
pad1: Source [fmt:UYVY2X8/320x240]
-> 'OMAP3 ISP resizer output':0 [ENABLED]
  • Hi John,

    If you have properly working resizer when using the /dev/omap-resizer probably the issue deus to the changing the /dev/omap-resizer to /dev/video5. Could you give more detailed description about how you make this changing?

    BR

    Tsvetolin Shulev

  • Hi 

    I am currently using gumstix with the same code tested on the evaluation board but it wont work with /dev/omap-resizer because media-ctl does not have that.

    With media-ctl, i managed to link up the video5 input and video6 output.

    In the linux folder in dmai under omap3530 , theres the Resizer.c where i changed made some modifications and get it to compile.

    It is able to acquire /dev/video5 for the open(/dev/video5, O_RDWR) but the resizer_config will fail.  

    Thanks.

  • Hi John,

    Could you compare booting log from both boards and search for some issues like errors or warnings in the gumstix board booting log?

    Also you can check the permissions of the /dev/video5 file and compare it on both boards.

    BR

    Tsvetolin Shulev

  • I am using a DM3730, 3.5 kernel and tvp5150 decoder

    The video looks great with a 720x480 resolution, and the CCDC is de-interlacing the video in /dev/video2 CCDC output.

    However, for my needs the video must be resized.
    In media-ctl, i use the pipeline (sensor -> ccdc -> resizer -> resizeroutput)
    The image, coming from the resizer output /dev/video6, is split into a top and bottom half.
    Both halves are identical where everything in the video is too wide and too short but the final image is in their resized resolution.

    Read from a website that:
    CCDC can't deinterlace frames sent to the resizer.
    The deinterlacing process takes place at the CCDC output DMA engine when writing the frames to memory.
    How can i merge them together into a final image?