From: "Jakub Piotr Cłapa" <jpc-ml@zenburn.net>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media <linux-media@vger.kernel.org>
Subject: [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock]
Date: Fri, 26 Jul 2013 17:37:36 +0200 [thread overview]
Message-ID: <51F297C0.1080501@zenburn.net> (raw)
In-Reply-To: <51F22A58.9030208@ti.com>
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 the
middle of doing some "bisecting" to figure out some unrelated problems
with omap3isp so in a couple days I may have more data about which
versions work and which do not.
> 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 any alternatives I should look into? IIUC
to use omapfb I would need to manually copy RGB data into the
framebuffer on each frame.
--
regards,
Jakub Piotr Cłapa
LoEE.pl
next prev parent reply other threads:[~2013-07-26 15:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 1:00 [omap3isp] xclk deadlock Jakub Piotr Cłapa
2013-07-04 20:21 ` Jakub Piotr Cłapa
2013-07-04 21:11 ` Laurent Pinchart
2013-07-04 22:36 ` Jakub Piotr Cłapa
2013-07-05 10:48 ` Laurent Pinchart
2013-07-12 14:44 ` Jakub Piotr Cłapa
2013-07-17 12:50 ` Laurent Pinchart
2013-07-17 22:17 ` Jakub Piotr Cłapa
2013-07-26 15:51 ` Laurent Pinchart
2013-07-26 23:51 ` Jakub Piotr Cłapa
2013-07-26 7:50 ` Tomi Valkeinen
2013-07-26 15:37 ` Jakub Piotr Cłapa [this message]
2013-07-26 15:52 ` [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock] Laurent Pinchart
2013-07-26 19:02 ` Jakub Piotr Cłapa
2013-07-26 19:13 ` Laurent Pinchart
2013-07-29 6:19 ` Tomi Valkeinen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51F297C0.1080501@zenburn.net \
--to=jpc-ml@zenburn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=tomi.valkeinen@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox