From: Robert Jarzmik <robert.jarzmik@free.fr>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Mike Turquette <mturquette@linaro.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: pxa: fix pxa27x_clocks_init scope
Date: Mon, 02 Feb 2015 21:17:58 +0100 [thread overview]
Message-ID: <871tm8awzt.fsf@free.fr> (raw)
In-Reply-To: <54CFD481.7050108@codeaurora.org> (Stephen Boyd's message of "Mon, 02 Feb 2015 11:48:17 -0800")
Stephen Boyd <sboyd@codeaurora.org> writes:
> On 01/31/15 14:37, Robert Jarzmik wrote:
>> As pxa27x_clocks_init() is called from early boot stage, it has to be
>> reachable from pxa architecture code, as are pxa25x_clocks_init() and
>> pxa2xx_clock_init().
>>
>> Remove the static declaration, which was introduced before the order
>> issue between clocks and the timer was discovered (ie. the clocks have
>> to be available before the timer, all of this before initcalls are
>> called).
>>
>> Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
>
> Is this supposed to go through the clk tree?
Ah you've got a point, it's a bit embarrassing, see below ...
> $ git grep pxa27x_clocks_init
> drivers/clk/pxa/clk-pxa27x.c:static int __init pxa27x_clocks_init(void)
> drivers/clk/pxa/clk-pxa27x.c:postcore_initcall(pxa27x_clocks_init);
> drivers/clk/pxa/clk-pxa27x.c: pxa27x_clocks_init();
>
> Where's the early boot stage architecture calling code?
It's there :
- https://lkml.org/lkml/2015/1/12/1057
- which ended up here in pxa/for-next tree:
https://github.com/rjarzmik/linux/commit/a494a74dc52532ed0cef4633db007a08f847a0a8
Which happens to be my tree ...
Please forget about this patch, I don't know how I ended up doing this patch
... lack of coffee probably.
Cheers.
--
Robert
prev parent reply other threads:[~2015-02-02 20:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-31 22:37 [PATCH] clk: pxa: fix pxa27x_clocks_init scope Robert Jarzmik
2015-02-02 19:48 ` Stephen Boyd
2015-02-02 20:17 ` Robert Jarzmik [this message]
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=871tm8awzt.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=sboyd@codeaurora.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