public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Kevin Hilman <khilman@linaro.org>
Cc: Mike Turquette <mturquette@linaro.org>,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	Andrew Lunn <andrew@lunn.ch>, Shawn Guo <shawn.guo@linaro.org>,
	Jason Cooper <jason@lakedaemon.net>,
	Arnd Bergmann <arnd@arndb.de>,
	Tomasz Figa <tomasz.figa@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Olof Johansson <olof@lixom.net>,
	Ezequiel Garcia <ezequiel.garcia@free-electrons.com>,
	Boris BREZILLON <b.brezillon@overkiz.com>,
	Sascha Hauer <kernel@pengutronix.de>,
	linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH v3] clk: respect the clock dependencies in of_clk_init
Date: Wed, 26 Mar 2014 17:02:40 +0100	[thread overview]
Message-ID: <5332FA20.4010206@free-electrons.com> (raw)
In-Reply-To: <CAGa+x85XLDZqCkz9R95d2Vj9eODx4q8W=9QhmMfivdPf2GdsaQ@mail.gmail.com>

On 26/03/2014 16:19, Kevin Hilman wrote:
> [+ imx6 maintainers ]
> 
> On Thu, Mar 20, 2014 at 8:52 PM, Mike Turquette <mturquette@linaro.org> wrote:
>> Quoting Gregory CLEMENT (2014-02-28 02:46:12)
>>> Hi Mike,
>>>
>>> On 24/02/2014 19:10, Gregory CLEMENT wrote:
>>>> Until now the clock providers were initialized in the order found in
>>>> the device tree. This led to have the dependencies between the clocks
>>>> not respected: children clocks could be initialized before their
>>>> parent clocks.
>>>>
>>>> Instead of forcing each platform to manage its own initialization order,
>>>> this patch adds this work inside the framework itself.
>>>>
>>>> Using the data of the device tree the of_clk_init function now delayed
>>>> the initialization of a clock provider if its parent provider was not
>>>> ready yet.
>>>>
>>>> The strict dependency check (all parents of a given clk must be
>>>> initialized) was added by Boris BREZILLON
>>>
>>> Are you ok with this version?
>>> Will you take it for 3.15?
>>> Or maybe you expected that it will be part of a pull request?
>>>
>>> However as it is modifying the core of the framework I thought that you
>>> would take it and apply yourself.
>>
>> Hi Gregory,
>>
>> I have taken this into clk-next. If no regressions pop up over the next
>> few days then it should go into 3.15.
> 
> $SUBJECT patch (as commit 1771b10d605) is in -next has been fingered
> by bisection to be the reason behind boot failures[1] on imx6 wand
> boards in the last several -next kernels.
> 
> Reverting the patch on top of next/master gets these boards booting again.
> 
> The boot failures result in no console output, so I haven't done any
> further debugging.

I don't have any imx6 board, but should it be possible for you or the imx6
maintainer to add earlyprintk to see exactly what happen here?


Thanks,

Gregory


> 
> Kevin
> 
> [1] http://lists.linaro.org/pipermail/kernel-build-reports/2014-March/002927.html
> 
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
> 


-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2014-03-26 16:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-24 18:10 [PATCH v3] clk: respect the clock dependencies in of_clk_init Gregory CLEMENT
2014-02-28 10:46 ` Gregory CLEMENT
     [not found]   ` <20140321035233.32624.98694@quantum>
2014-03-26 15:19     ` Kevin Hilman
2014-03-26 16:02       ` Gregory CLEMENT [this message]
2014-03-26 16:22         ` Fabio Estevam
2014-03-26 19:50           ` Gregory CLEMENT

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=5332FA20.4010206@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=andrew@lunn.ch \
    --cc=arnd@arndb.de \
    --cc=b.brezillon@overkiz.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=jason@lakedaemon.net \
    --cc=kernel@pengutronix.de \
    --cc=khilman@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@linaro.org \
    --cc=olof@lixom.net \
    --cc=sebastian.hesselbarth@gmail.com \
    --cc=shawn.guo@linaro.org \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=tomasz.figa@gmail.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