From: khilman@linaro.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clk: reverse default clk provider initialization order in of_clk_init()
Date: Mon, 31 Mar 2014 08:00:18 -0700 [thread overview]
Message-ID: <7h1txi76rh.fsf@paris.lan> (raw)
In-Reply-To: <20140329084147.5762.51815@quantum> (Mike Turquette's message of "Sat, 29 Mar 2014 01:41:47 -0700")
Mike Turquette <mturquette@linaro.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@samsung.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
WARNING: multiple messages have this Message-ID (diff)
From: Kevin Hilman <khilman@linaro.org>
To: Mike Turquette <mturquette@linaro.org>
Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, b.brezillon@overkiz.com,
festevam@gmail.com, shawn.guo@linaro.org,
nicolas.ferre@atmel.com, sebastian.hesselbarth@gmail.com,
plagnioj@jcrosoft.com
Subject: Re: [PATCH] clk: reverse default clk provider initialization order in of_clk_init()
Date: Mon, 31 Mar 2014 08:00:18 -0700 [thread overview]
Message-ID: <7h1txi76rh.fsf@paris.lan> (raw)
In-Reply-To: <20140329084147.5762.51815@quantum> (Mike Turquette's message of "Sat, 29 Mar 2014 01:41:47 -0700")
Mike Turquette <mturquette@linaro.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@samsung.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
next prev parent reply other threads:[~2014-03-31 15:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 10:43 [PATCH] clk: reverse default clk provider initialization order in of_clk_init() Sylwester Nawrocki
2014-03-27 10:43 ` Sylwester Nawrocki
2014-03-27 10:49 ` Sylwester Nawrocki
2014-03-27 10:49 ` Sylwester Nawrocki
2014-03-29 8:41 ` Mike Turquette
2014-03-31 15:00 ` Kevin Hilman [this message]
2014-03-31 15:00 ` Kevin Hilman
2014-03-31 17:05 ` Mike Turquette
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=7h1txi76rh.fsf@paris.lan \
--to=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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.