linux-kernel - Re: [PATCH] clk: reverse default clk provider initialization order in of_clk

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <7h1txi76rh.fsf@paris.lan>
Date:	Mon, 31 Mar 2014 08:00:18 -0700
From:	Kevin Hilman <khilman@...aro.org>
To:	Mike Turquette <mturquette@...aro.org>
Cc:	Sylwester Nawrocki <s.nawrocki@...sung.com>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	b.brezillon@...rkiz.com, festevam@...il.com, shawn.guo@...aro.org,
	nicolas.ferre@...el.com, sebastian.hesselbarth@...il.com,
	plagnioj@...osoft.com
Subject: Re: [PATCH] clk: reverse default clk provider initialization order in of_clk_init()

Mike Turquette <mturquette@...aro.org> writes:

> Quoting Sylwester Nawrocki (2014-03-27 03:43:32)
>> This restores the default clocks registration order as parsed from
>> devicetree, i.e. as before commit 1771b10d605d26ccee771a7fb4b08718
>> "clk: respect the clock dependencies in of_clk_init", for when there
>> is no explicit parent clock dependencies between clock providers
>> specified in the device tree.
>> 
>> It prevents regressions (boot failure, division by 0 errors) on
>> imx and exynos platforms.
>> 
>> Signed-off-by: Sylwester Nawrocki <s.nawrocki@...sung.com>
>
> I pulled this into clk-next but it didn't seem to get picked up by
> linux-next in time for today's build. Let's test the next linux-next to
> insure that the regressions are gone. If not then I'll likely need to
> drop "clk: respect the clock dependencies in of_clk_init" from clk-next
> for 3.15.

It looks like all the boot failures caused by this problem are gone as
of next-20140331[1], so it looks good to me.

Kevin

[1] http://lists.linaro.org/pipermail/kernel-build-reports/2014-March/002988.html
--
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/