• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Subscribers 98 subscribers
  • Views 529 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.

What does DM365IPNC use for the capture driver ?

TIG
Intellectual 270 points

Hello.

 

I am analyzing the capture part of DM365IPNC application . This is AV_server directory.

Now, I cannot find the source code that defines (or uses) the capture device file .

 

What does DM365IPNC use for the capture driver ?

Where is the source code that defines the capture device file ?

 

I looked for the video directory (IPNetCam/ipnc/av_capture/application/ipnc/multimedia/av_server/src/video)

and drv directory (IPNetCam/ipnc/av_capture/framework/drv).

 

Relating question :

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/f/100/p/53425/189539.aspx#189539

  • 0
    TI__Mastermind 19985 points

    Hi,

    For the capture drivers on IPNC, please refer to the following list of source code files:

    1.  framework/drv/usermod/src/drv_capture.c

    2. framework/drv/usermod/src/drv_resz.c

    Finally, these drivers call the lower level CSL layer for the individual components like ISIF (ccdc), IPIPE, IPIPEIF, RSZ, LDC etc.

    The application code which uses the capture driver can be seen in application/ipnc/multimedia/av_server/src/video/videoCaptureThr.c

    Hope this helps.

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it has answered your question. Thanks.

  • 0 in reply to Anshuman Saxena
    Intellectual 270 points

    Hi, thanks for your replay.

     

    What is the capture driver described in menuconfig ?

    What name is the device file in OS ( /dev/*** ) ? /dev/csl0 ?

    I do not understand capture driver's substance.

  • 0 in reply to TIG
    TI__Mastermind 19985 points

    Hi,

    Please refer to csl_sysLinuxDrv.c in av_capture/framework/csl/kermod/src/system.

    As i had mentioned earlier, the driver architecture is little different from the V4L2 interface and we have driver for each individual component of the VPFE. In csl_soc.h, you can find the mapping of each /dev/csl[0-9] devices.

    Hope this helps.

    Regards,

    Anshuman

    PS: Please mark this post as verified, if you think it answered your question. Thanks.

  • 0 in reply to Anshuman Saxena
    Intellectual 270 points

    Hi, Anshuman.

    Thanks for your replay.

     

    I did not understand the flow of the capture processing.

    I'm sorry.

     

    The image sensor is controlled by individual component of the VPFE (IPIPE, H3A, CCDC). 

    V4l2 and DRV (wrapper library) is VPFE interface.  OK ?

     

  • 0 in reply to TIG
    TI__Mastermind 19985 points

    Hi,

    Have you already referred to the AV Server Design Guide that exist in the IPNC Ref Design release documents?

    Regards,

    Anshuman

  • 0 in reply to Anshuman Saxena
    Intellectual 270 points

    Hi,

     Thank you.

     

    I saw IPNetCam Reference Design on DM365 AV Server Design Guide (P8 Software Architecture, P13 Data Flow)

    and LSP 2.10 DaVinci Linux Drivers  (P42 Figure 2-4. DM365 Video Driver Architecture).

    Figure 2-4 drivers architecture use V4l2 frame work (This is document for DM365EVM).

    P8 Software Architecture is not seen V4l2.

    IPNC uses the DRV rapper library instead of V4l2..(I thought that DRV low layer used V4l2. But DRV uses VPFE driver directly without V4l2 ).