Linux/TMS320DM8168: TI8168 VIN[1]B_VSYNC pinmux question

CY said:

but we can't get the video at VIN1B,There is what we try:

1.we notice that  VIN[1]B_HSYNC_DE is a multipixed pin. so we cut the DE line.the picture is better,but still half of screen not display.

CY said:

1.the VIN[1]B_HSYNC_DE pin,we choose SYSTEM_CAPT_VIDEO_CAPTURE_MODE_SINGLE_CH_NON_MUX_DISCRETE_SYNC_HSYNC_VSYNC  mode.

the DE pin will effect the capture.When we cut the DE pin at gv7601 hardward design,the picture is better. So i want to know,do we have any way to get it at software?

You can try to use the default muxmode 0 for PINCTRL27/0x48140868 (VIN[1]B_HSYNC_DE). Make sure the SW never muxmode this signal to any pin, by default [2:0] MUXMODE is 0x0, make sure it stays at this default value.

CY said:

2.we check the 0x48140870 about VIN[1]B_VSYNC,we found the value is 0x00000002,so we change it at kernel.

    at the board boot up,the 0x48140870 value is 0x00000003,the pin is at VIN[1]B_VSYNC mode.but we run the application,the register value is change to 2.

    here is some logs.

root@dm816x-evm:~# devmem2 0x48140870
/dev/mem opened.
Memory mapped at address 0x402e5000.
Read at address 0x48140870 (0x402e5870): 0x00000002

CY said:

2.I think somewhere at DVRRDK change the 0x48140870 register value.we try to force its value at kernel or vps_platformTI816x.c,but still failed,i will change back.So, I want to know how to force the register 0x48140870 to be 0x00000003.

When you made your pinmux like described in the below wiki, make sure that nothing is overwriting you pinmux setting afterwards in kernel, firmware or application. If you are sure that application code (not firmware code, not kernel code) is changing your pinmux, then you should fix your application, this can not be handled by kernel code.

Regards,
Pavel