public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: "Jakub Piotr Cłapa" <jpc-ml@zenburn.net>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: [omap3isp] xclk deadlock
Date: Thu, 04 Jul 2013 23:11:13 +0200	[thread overview]
Message-ID: <2398527.WgqgO0AkRo@avalon> (raw)
In-Reply-To: <51D5D967.1030306@zenburn.net>

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 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).

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 they were not present in the omap3isp/xclk branch.

I've now deleted the branch from the public tree, sorry for the confusion.

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

Laurent Pinchart


  reply	other threads:[~2013-07-04 21:10 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 [this message]
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=2398527.WgqgO0AkRo@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=jpc-ml@zenburn.net \
    --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