• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 97 subscribers
  • Views 386 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

VPFE Capture driver from LSP2.10 in encodedecode demo - interlaced mode

Jinh
Expert 2315 points

Other Parts Discussed in Thread: TVP5146, TVP7002

I am trying to insert data (bargraph type on edge) per field on the DM365 and have questions about one-shot mode and continuous mode if it applies to the Pass-Through setting in the encodedecode demo code.  Firstly when I run fbdev_loopback demo then the original fields from the input buffer is just coipied over to the output/display buffer and my field data is kept as is and displayed but when I run the encodedecode demo and even in -p mode my second field is duplicated into my first field and I loose half my data.  From the VPFE and v4l2 documentation I can see that when the resizer and encoder is enabled this will happen - also something to do with continouos mode - but from the comments in the code in encodedecode demo and what I understand the data in passthrough mode should not change like I see it is doing now.  Please help me to resolve if there are problems with buffer handling or setting up the attributed of the mode.  In my application, derived from encodedecode, I do not wish to use the resizer or encoder and want to keep field information in place like in the fbdev_loopback demo. 

I see my bootargs is still set up for continuous mode but can I run this demo to it full functionality when it is not set up in continuous mode?  I will try and confirm that now but need answers on the theory please.

Thanks, Jinh T

  • 0
    Expert 2315 points

    The bootargs setting for the image processing module is set to continuous mode (dm365_imp.oper_mode=0) but changing it to 1 causes the demo (encodedecode) not to operate anymore.  The setting for this is also zero for fbdev_loopback demo so this is not the problem for de-interlacing in encodedecode demo.  What should I change in encodedecode demo together with pass-through mode (I do not need encoder or resizer in my application) to keep my field data and not have automatic de-interlacing done?

    I also want to find out why the encodedecode demo keep working for setting the capture driver (davinci_capture.driver_type) to either 4 (according to SPRUGP6 setting for TVP7002) and to 1 (setting for TVP5146) does not make a difference in operation of my DM365EVM?

    Thanks, Jinh T.