Re: [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock]

2013-07-29 Thread Tomi Valkeinen
On 26/07/13 18:37, Jakub Piotr Cłapa wrote: Using omapfb, or...? I hope not omap_vout, because that's rather unmaintained =). Laurent's live application is using the V4L2 API for video output (to get free YUV conversion and DMA) so I guess this unfortunatelly counts as using omap_vout. Are

[omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock]

2013-07-26 Thread Jakub Piotr Cłapa
Dear Tomi, Thanks for your reply. On 26.07.13 09:50, Tomi Valkeinen wrote: Sounds like something is enabling/disabling dispc interrupts after the clocks have already been turned off. So what's the context here? What kernel? This was on 3.10 from Laurent's board/beagle/mt9p031 branch. I am

Re: [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock]

2013-07-26 Thread Laurent Pinchart
Hi Jakub, On Friday 26 July 2013 17:37:36 Jakub Piotr Cłapa wrote: Dear Tomi, Thanks for your reply. On 26.07.13 09:50, Tomi Valkeinen wrote: Sounds like something is enabling/disabling dispc interrupts after the clocks have already been turned off. So what's the context here?

Re: [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock]

2013-07-26 Thread Jakub Piotr Cłapa
On 26.07.13 17:52, Laurent Pinchart wrote: Using omapfb, or...? I hope not omap_vout, because that's rather unmaintained =). Laurent's live application is using the V4L2 API for video output (to get free YUV conversion and DMA) so I guess this unfortunatelly counts as using omap_vout. Are

Re: [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock]

2013-07-26 Thread Laurent Pinchart
Hi Jakub, On Friday 26 July 2013 21:02:35 Jakub Piotr Cłapa wrote: On 26.07.13 17:52, Laurent Pinchart wrote: Using omapfb, or...? I hope not omap_vout, because that's rather unmaintained =). Laurent's live application is using the V4L2 API for video output (to get free YUV conversion