From: linux@armlinux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: sa1100: register clocks early
Date: Tue, 23 Aug 2016 09:58:54 +0100 [thread overview]
Message-ID: <20160823085854.GD1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CALT56yPLMiQZaeSxmo3xz_+6c11BO-hWSEN2ex-ziJGZdZDY6w@mail.gmail.com>
On Tue, Aug 23, 2016 at 04:47:08AM +0300, Dmitry Eremin-Solenikov wrote:
> 2016-08-19 14:51 GMT+03:00 Russell King <rmk+kernel@armlinux.org.uk>:
> > Since we switched to use pxa_timer, we need to provide the OSTIMER0
> > clock. However, as the clock is initialised early, we need to provide
> > the clock early as well, so that pxa_timer can find it. Adding the
> > clock to the clkdev table at core_initcall() time is way too late.
>
> This worked for me before, so maybe the init order of other kernel parts
> has changed. Anyway:
>
> Acked-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
It worked in so far as we fell back to the non-clock based code, so
things continued to work. However, a warning was printed at each
boot.
I don't think this ever worked. Timers are setup very early in the
boot process (going back to 0.99.x times), and core_initcall() has
always been after that, after pid1 has been created.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
prev parent reply other threads:[~2016-08-23 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-19 11:51 [PATCH 2/2] ARM: sa1100: register clocks early Russell King
2016-08-23 1:47 ` Dmitry Eremin-Solenikov
2016-08-23 8:58 ` Russell King - ARM Linux [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=20160823085854.GD1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).