From: "Jakub Piotr Cłapa" <jpc-ml@zenburn.net>
To: linux-media <linux-media@vger.kernel.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [omap3isp] xclk deadlock
Date: Thu, 04 Jul 2013 22:21:59 +0200 [thread overview]
Message-ID: <51D5D967.1030306@zenburn.net> (raw)
In-Reply-To: <51D37796.2000601@zenburn.net>
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: 36286390193922d148e7a3db0676747a20f2ed66 at the time of writing)
For reference:
1. This was a known problem since early January [1] (reported by Laurent).
2. Mike Turquette had submitted patches that made the clock framework
(partially) reentrant. [2][3][4]
3. My code is just a rebase of the Laurent's omap3isp/xclk branch on the
Mike's clk-next (so it's based on 3.10-rc3).
[1]: https://lkml.org/lkml/2013/1/6/169
[2]: http://thread.gmane.org/gmane.linux.kernel/1448446/focus=1448448
[3]: http://thread.gmane.org/gmane.linux.ports.arm.kernel/182198
[4]: http://patches.linaro.org/15676/
--
regards,
Jakub Piotr Cłapa
LoEE.pl
next prev parent reply other threads:[~2013-07-04 20:22 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 [this message]
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 ` [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=51D5D967.1030306@zenburn.net \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.