Maybe this is more of a OMAP specific question, but I'm using a beagleboard-xm with a custom image sensor on a 3.0.17 kernel. Everything configures ok with: media-ctl -r media-ctl -l '"xrtcam 2-0048":0->"OMAP3 ISP CCDC":0[1]' media-ctl -l '"OMAP3 ISP CCDC":1->"OMAP3 ISP CCDC output":0[1]' media-ctl -f '"xrtcam 2-0048":0 [Y8 640x1440]' media-ctl -f '"OMAP3 ISP CCDC":1 [Y8 640x1440]' media-ctl -e 'OMAP3 ISP CCDC output' root@beagleboard:~# ./setup.sh Resetting all links to inactive Setting up link 16:0 -> 5:0 [1] Setting up link 5:1 -> 6:0 [1] Setting up format Y8 640x1440 on pad irtcam 2-0048/0 Format set: Y8 640x1440 Setting up format Y8 640x1440 on pad OMAP3 ISP CCDC/0 Format set: Y8 640x1440 Setting up format Y8 640x1440 on pad OMAP3 ISP CCDC/1 Format set: Y8 640x1440 /dev/video2 But when I go to capture, with: yavta -c2 -p -F --skip 0 -f Y8 -s 640x1440 /dev/video2 I don't seem to get any interrupts. Actually I get some HS_VS_IRQ after I launch yavta, but before I press return at the "Press enter to start capture" prompt. After that, I don't believe I am getting any interrupts. The one problem I see is that my sensor is always spewing data into the CCDC on HS,VS, PCLK, and D0 to D7. I know I have been told with other sensors that I need to only turn XCLK on to the sensor when I am capturing. Could this be my problem here? What exactly happens if you are always sending data? Does the ISP get hung up? Thanks for any pointers, Chris -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
