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

2013-07-28 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_vo

Re: [omap3isp] xclk deadlock

2013-07-26 Thread Jakub Piotr Cłapa
Dear Laurent, The offending commit is b2da46e52fe7871cba36e1a435844502c0eccf39 After reverting it I get good image on v3.5-rc1. Unfortunatelly trying to revert it on the board/beagle/mt9p031 branch causes conflicts and I am too tired to even try to fix them right now. The hanging unfortunate

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 fr

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 there

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 conte

Re: [omap3isp] xclk deadlock

2013-07-26 Thread Laurent Pinchart
Hi Jakub, On Thursday 18 July 2013 00:17:19 Jakub Piotr Cłapa wrote: > On 17.07.13 14:50, Laurent Pinchart wrote: > > Hi Jakub, > > > >> 3. After setting up a simple pipeline using media-ctl[2] I get "CCDC > >> won't become idle errors". If I do this after running "live" I also get > >> (unless i

[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 in

Re: [omap3isp] xclk deadlock

2013-07-26 Thread Tomi Valkeinen
On 17/07/13 15:50, Laurent Pinchart wrote: > Hi Jakub, > > (CC'ing Tomi Valkeinen) > > On Friday 12 July 2013 16:44:44 Jakub Piotr Cłapa wrote: >> 2. When exiting from live the kernel hangs more often then not >> (sometimes it is accompanied by "Unhandled fault: external abort on >> non-linefetc

Re: [omap3isp] xclk deadlock

2013-07-17 Thread Jakub Piotr Cłapa
On 17.07.13 14:50, Laurent Pinchart wrote: Hi Jakub, 3. After setting up a simple pipeline using media-ctl[2] I get "CCDC won't become idle errors". If I do this after running "live" I also get (unless it hangs) the CCDC Register dump [1]. Otherwise I only get the stream of kernel log messages

Re: [omap3isp] xclk deadlock

2013-07-17 Thread Laurent Pinchart
Hi Jakub, (CC'ing Tomi Valkeinen) On Friday 12 July 2013 16:44:44 Jakub Piotr Cłapa wrote: > Hi Laurent, > > On 05.07.13 12:48, Laurent Pinchart wrote: > >> Thanks for the explanation. It would be great if you could update your > >> board/beagle/mt9p031 branch and include the discussed changes.

Re: [omap3isp] xclk deadlock

2013-07-12 Thread Jakub Piotr Cłapa
Hi Laurent, On 05.07.13 12:48, Laurent Pinchart wrote: Thanks for the explanation. It would be great if you could update your board/beagle/mt9p031 branch and include the discussed changes. Done. Could you please test it ? Thanks for you help. There are no errors about the clocks or regulator

Re: [omap3isp] xclk deadlock

2013-07-05 Thread Laurent Pinchart
Hi Jakub, On Friday 05 July 2013 00:36:44 Jakub Piotr Cłapa wrote: > Hi Laurent, > > On 04.07.13 23:11, Laurent Pinchart wrote: > > The omap3isp/xclk clock branch was used only to push patches to the media > > tree, I should have deleted it afterwards. Mike's reentrancy patches were > > already m

Re: [omap3isp] xclk deadlock

2013-07-04 Thread Jakub Piotr Cłapa
Hi Laurent, On 04.07.13 23:11, Laurent Pinchart wrote: The omap3isp/xclk clock branch was used only to push patches to the media tree, I should have deleted it afterwards. Mike's reentrancy patches were already merged (or scheduled for merge) in mainline at that time, and for technical reasons t

Re: [omap3isp] xclk deadlock

2013-07-04 Thread Laurent Pinchart
Hi Jakub, On Thursday 04 July 2013 22:21:59 Jakub Piotr Cłapa wrote: > Hi again, > > Sorry for the noise, but I believe the information below may be useful > until everything is merged into mainline. > > I write to say that I managed to find a fix for the ISP clock deadlock. > My branch can be

Re: [omap3isp] xclk deadlock

2013-07-04 Thread Jakub Piotr Cłapa
Hi again, Sorry for the noise, but I believe the information below may be useful until everything is merged into mainline. I write to say that I managed to find a fix for the ISP clock deadlock. My branch can be found at: https://github.com/LoEE/linux/tree/omap3isp/xclk (SHA: 36286390193922

[omap3isp] xclk deadlock

2013-07-02 Thread Jakub Piotr Cłapa
Hi everyone, Background: I was trying to get the mt9p031 sensor working on a BeagleBoard xM with a patched 3.9.8 kernel[1] or with the Laurent Pinchart's omap3isp/xclk branch[2]. I had this hardware working quite well under linux 3.2.8 and 3.2.24 with a patchset from Max Galemin but I had ke