linux-kernel - Re: [PATCH v3] clk: respect the clock dependencies in of_clk_init

Open Source and information security mailing list archives

Date:	Wed, 26 Mar 2014 17:02:40 +0100
From:	Gregory CLEMENT <gregory.clement@...e-electrons.com>
To:	Kevin Hilman <khilman@...aro.org>
CC:	Mike Turquette <mturquette@...aro.org>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Andrew Lunn <andrew@...n.ch>, Shawn Guo <shawn.guo@...aro.org>,
	Jason Cooper <jason@...edaemon.net>,
	Arnd Bergmann <arnd@...db.de>,
	Tomasz Figa <tomasz.figa@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Olof Johansson <olof@...om.net>,
	Ezequiel Garcia <ezequiel.garcia@...e-electrons.com>,
	Boris BREZILLON <b.brezillon@...rkiz.com>,
	Sascha Hauer <kernel@...gutronix.de>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>
Subject: Re: [PATCH v3] clk: respect the clock dependencies in of_clk_init

On 26/03/2014 16:19, Kevin Hilman wrote:
> [+ imx6 maintainers ]
> 
> On Thu, Mar 20, 2014 at 8:52 PM, Mike Turquette <mturquette@...aro.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@...ts.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives