Laurent Pinchart wrote: ... > That's the ideal situation: sensors should not produce any data (or rather any > transition on the VS/HS signals) when they're supposed to be stopped. > Unfortunately that's not always easy, as some dumb sensors (or sensor-like > hardware) can't be stopped. The ISP driver should be able to cope with that in > a way that doesn't kill the system completely. > > I've noticed the same issue with a Caspa camera module and an OMAP3503-based > Gumstix. I'll try to come up with a good fix. Hi Laurent, others, Do you think the cause for this is that the system is jammed in handling HS_VS interrupts triggered for every HS? A quick fix for this could be just choosing either VS configuration when configuring the CCDC. Alternatively, HS_VS interrupts could be just disabled until omap3isp_configure_interface(). But as the sensor is sending images all the time, proper VS configuration would be needed, or the counting of lines in the CCDC (VD* interrupts) is affected as well. The VD0 interrupt, which is used to trigger an interrupt near the end of the frame, may be triggered one line too early on the first frame, or too late. But this is up to a configuration. I don't think it's a real issue to trigger it one line too early. Anything else? Cheers, -- Sakari Ailus sakari.ailus@xxxxxxxxxxxxxxxxxxxxxxxxxx -- 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
