• State TI Thinks Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 101 subscribers
  • Views 431 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.

AM5728: VIP module loading

satyanarayana P G64
Expert 1330 points

Part Number: AM5728

hi,

we have three video sources for capturing video in AM5728 through VIP module, but loading of modules is different in each instance of boot.

I need to have a fixed routine, so that capturing of video will be similar in all boot instance.

Because of randomization of module assignment, video capturing of particular video varies for each instance.

please suggest any method for fixed routine of module assignment.

BR

satya

  • 0
    TI__Mastermind 45035 points

    Hello Satya,

    I am assuming you are trying to control the nodes created under /dev/video* directory. I recommend you to please search "udev fixed device name" and you will find a lot of references online.

    Regards,
    Krunal 

  • 0 in reply to Krunal Bhargav34
    Expert 1260 points

    hi,

    thank you for your suggestion, but need further guidance from you.

    we have similar devices on same vip, hence the udev separation is not happening giving out error same vip instance.

    BR

    satya

  • 0 in reply to Krunal Bhargav34
    Expert 1330 points

    hi,

    thank you for your suggestion, but need further guidance from you.

    we have similar devices on same vip, hence the udev separation is not happening giving out error same vip instance.

    BR

    satya

  • 0 in reply to satyanarayana P G64
    TI__Mastermind 45035 points

    Hello Satya,

    Based on my discussion with our developers, here are a couple of commands you use to figure out the bus info:

    root@am57xx-evm:~# ls -al /dev/v4l/by-path/
drwxr-xr-x    2 root     root           100 Jul  7 03:14 .
drwxr-xr-x    3 root     root            60 Jul  7 03:14 ..
lrwxrwxrwx    1 root     root            12 Jul  7 03:14 platform-48990000.vip-video-index0 -> ../../video1
lrwxrwxrwx    1 root     root            12 Jul  7 03:14 platform-489d0000.vpe-video-index0 -> ../../video0
lrwxrwxrwx    1 root     root            13 Jul  7 03:14 platform-omapdrm.0-video-index0 -> ../../video10
root@am57xx-evm:~# v4l2-dbg --info -d /dev/v4l/by-path/platform-48990000.vip-video-index0 
Driver info:
        Driver name   : vip
        Card type     : vip
        Bus info      : platform:vip2:vin3a:stream0
        Driver version: 4.19.38
        Capabilities  : 0x85200001
                Video Capture
                Read/Write
                Streaming
                Extended Pix Format
                Device Capabilities
root@am57xx-evm:~#

    The “v4l2-dbg –info” basically issue a VIDIOC_QUERYCAP ioctl of the device node. If you look at the “Bus info”, it shows which vip instance and which vin port that specific device node represent. This is only going to work on PSDK5.0+.

    Regards,
    Krunal