On Tue, Jul 05, 2011 at 05:02:52PM +0200, Laurent Pinchart wrote: > On Tuesday 05 July 2011 16:38:07 Sakari Ailus wrote: > > On Tue, Jul 05, 2011 at 02:48:57PM +0100, Jonathan Cameron wrote: > > > On 07/05/11 13:19, Sakari Ailus wrote: > > > > On Tue, Jul 05, 2011 at 12:22:06PM +0100, Jonathan Cameron wrote: > > > >> Hi Laurent, > > > >> > > > >> I'm just trying to get an mt9v034 sensor working on a beagle xm. > > > >> Everything more or less works, except that after a random number > > > >> of frames of capture, I tend to get won't become idle messages > > > >> and the vd0 and vd1 interrupts tend to turn up at same time. > > > >> > > > >> I was just wondering if there are any known issues with the ccdc > > > >> driver / silicon that might explain this? > > > >> > > > >> I also note that it appears to be impossible to disable > > > >> HS_VS_IRQarch/arm/mach-s3c2410/Kconfig:# cpu frequency scaling > > > >> support > > > >> > > > >> despite the datasheet claiming this can be done. Is this a known > > > >> issue? > > > > > > > > The same interrupt may be used to produce an interrupt per horizontal > > > > sync but the driver doesn't use that. I remember of a case where the > > > > two sync signals had enough crosstalk to cause vertical sync interrupt > > > > per every horizontal sync. (It's been discussed on this list.) This > > > > might not be the case here, though: you should be flooded with HS_VS > > > > interrupts. > > > > > > As far as I can tell, the driver doesn't use either interrupt (except to > > > pass it up as an event). Hence I was trying to mask it purely to cut > > > down on the interrupt load. > > > > It does. This is the only way to detect the CCDC has finished processing a > > frame. > > We actually use the VD0 and VD1 interrupts for that, not the HS_VS interrupt. Right; I confused the two for a moment. Cheers, -- Sakari Ailus sakari.ailus@xxxxxx -- 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
