Re: omap3isp with DM3730 not working?!

[Laurent Pinchart <laurent.pinchart@ideasonboard.com>]

Hi Enrico,

On Monday 28 July 2014 15:18:04 Enrico wrote:
> On Mon, Jul 28, 2014 at 12:29 PM, Laurent Pinchart wrote:
> > On Monday 28 July 2014 10:30:17 Enrico wrote:
> >> On Mon, Jul 28, 2014 at 9:20 AM, Sakari Ailus wrote:
> >>> On Thu, Jul 24, 2014 at 05:57:30PM +0200, Enrico wrote:
> >>>> On Thu, Jul 24, 2014 at 5:34 PM, Michael Dietschi wrote:
> >>>>> Hello,
> >>>>> 
> >>>>> I have built a Poky image for Gumstix Overo and added support for a
> >>>>> TVP5151 module like described here http://www.sleepyrobot.com/?p=253.
> >>>>> It does work well with an Overo board which hosts an OMAP3530 SoC.
> >>>>> But when I try with an Overo hosting a DM3730 it does not work: yavta
> >>>>> just seems to wait forever :(
> >>>>> 
> >>>>> I did track it down to the point that IRQ0STATUS_CCDC_VD0_IRQ seems
> >>>>> never be set but always IRQ0STATUS_CCDC_VD1_IRQ
> >>> 
> >>> VD1 takes place in 2/3 of the frame, and VD0 in the beginning of the
> >>> last line. You could check perhaps if you do get VD0 if you set it to
> >>> take place on the previous line (i.e. the register value being height -
> >>> 3; please see ccdc_configure() in ispccdc.c).
> >>> 
> >>> I have to admit I haven't used the parallel interface so perhaps others
> >>> could have more insightful comments on how to debug this.
> >>> 
> >>>>> Can someone please give me a hint?
> >>>> 
> >>>> It's strange that you get the vd1_irq because it should not be set by
> >>>> the driver and never trigger...
> >>> 
> >>> Both VD0 and VD1 are used by the omap3isp driver, but in different
> >>> points of the frame.
> >> 
> >> Hi Sakari,
> >> 
> >> that's true in "normal" mode, but with bt656 patches VD1 is not used.
> > 
> > That's not correct, VD1 is used in both modes. In BT.656 mode VD1 is even
> > used to increment the frame counter in place of the HS_VS interrupt.
> 
> ...in your new patches. But sleepyrobot's are the old ones and i bet
> Michael is using those patches.

You're right. Maybe that's the first problem to be fixed though ;-) Michael, 
could you try using the "official" (and under development) BT.656 support code 
for the OMAP3 ISP driver ? I've just pushed the branch to

	git://linuxtv.org/pinchartl/media.git omap3isp/bt656

-- 
Regards,

Laurent Pinchart