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.

How to :remove input modules from dm365 evm

Other Parts Discussed in Thread: TVP5150, TVP7002, THS7353, TVP5146

Hi,

Now i have modified the demo on encoder on dm365 evm.Now for the project uitility, i have removed some input modules remainning the TVP5150 from the board,and connected the tvp5150 with the main chip(dm365) directly.But how could i do to remove the relative drivers from the kernel.Now i have disabled the tvp7002 driver in the dm365 menuconfig, but how to modify other relative source code.Another, what is the input method via tvp5150?? Is it ' Capture_Input_COMPOSITE '??

Regards

  • Hi !

    guizhong xu said:

    Is it ' Capture_Input_COMPOSITE '??

    Yes.

     

    I have had the experience of TVP5150 connecting to the DM365EVM.
    I advise you to remove (just comment out) all the other codecs (tvp5146, tvp7002, ths7353, mt9p031) in the file 'arch/arm/mach-davinci/board-dm365-evm.c' and add some
    info for tvp5150.
    See 'static struct vpfe_subdev_info vpfe_sub_devs[]'.

    Here is my HOWTO:
    http://e2e.ti.com/support/embedded/f/354/t/127715.aspx

    There are no modifications for encode-demo.
    I use '-y 2' option only.
    ./encode -y 2 -v test.264

    In my case it works.
    All this looks as if TVP5150 is used instead of TVP5146.

  • Hi,Senchuss

    Thanks for your answer.The board has run successfully in the case removing all the other drivers expect TVP5150.I have read the link you provided to me.It is not in the case as you said about dm365 kernel.I did not find the relative functions.Now I want to know the OVREALL ARCHITECTURE about I2C device driver in dm365 drivers.Can you give me some materials about this?My email is :gzhxu@163.com.Thanks again.

    Best regards.

  • I want to say one thing... If you want to make calls to I2C devices are already managed by the kernel,
    then you need to use 'I2C_SLAVE_FORCE' instead of 'I2C_SLAVE' in ioctl.
    For more details see "$DVSDK/psp/linux-2.6.32.17-psp03.01.01.39/Documentation/i2c/dev-interface".
    I could never imagine that there is a book about OVEREALL ARCHITECTURE about I2C device driver in dm365.
    Why to understand how it work?

    There are some simple calls and so on.

    Good luck!