Re: OMAP3 ISP deadlocks on my new arm

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



2011/4/21 Laurent Pinchart <laurent.pinchart@xxxxxxxxxxxxxxxx>:
> Hi Sakari,
>
> On Tuesday 19 April 2011 09:31:05 Sakari Ailus wrote:
>> 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?
>
> That was my initial guess, yes.
>
>> 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?

Hello Laurent,

> I've tried delaying the HS_VS interrupt enable to the CCDC configuration
> function, after configuring the bridge (and thus the HS/VS interrupt source
> selection). To my surprise it didn't fix the problem, I still get tons of
> HS_VS interrupts (100000 in about 2.6 seconds) that kill the system.
>
> I'll need to hook a scope to the HS and VS signals.

have you worked on this problem? Today in my setup I took a longer
cable and ran again into the hs/vs interrupt storm (it still works
with a short cable).
I can tackle this issue too, but to avoid double work I wanted to ask
if you worked out something in the meantime.

Best regards,

 Bastian Hecht

>
> --
> Regards,
>
> Laurent Pinchart
>
--
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


[Index of Archives]     [Linux Input]     [Video for Linux]     [Gstreamer Embedded]     [Mplayer Users]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]
  Powered by Linux