From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Jakub Piotr Cłapa" <jpc-ml@zenburn.net>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: [omap3isp] xclk deadlock
Date: Fri, 26 Jul 2013 10:50:48 +0300 [thread overview]
Message-ID: <51F22A58.9030208@ti.com> (raw)
In-Reply-To: <3227918.6DpNM0vnE9@avalon>
[-- Attachment #1: Type: text/plain, Size: 643 bytes --]
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-linefetch" in "dispc_write_irqenable" in omapdss).
>
> I'll pass this one to Tomi :-)
Sounds like something is enabling/disabling dispc interrupts after the
clocks have already been turned off.
So what's the context here? What kernel? Using omapfb, or...? I hope not
omap_vout, because that's rather unmaintained =).
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 901 bytes --]
next prev parent reply other threads:[~2013-07-26 7:50 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 [this message]
2013-07-26 15:37 ` [omapdss] fault in dispc_write_irqenable [was: Re: [omap3isp] xclk deadlock] Jakub Piotr Cłapa
2013-07-26 15:52 ` 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=51F22A58.9030208@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=jpc-ml@zenburn.net \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
/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