From: Marc.Zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: local timers: Allow boot CPU to have its timer running early
Date: Thu, 02 Jun 2011 17:56:55 +0100 [thread overview]
Message-ID: <1307033815.31098.31.camel@e102391-lin.cambridge.arm.com> (raw)
In-Reply-To: <20110602163152.GH32751@game.jcrosoft.org>
On Thu, 2011-06-02 at 18:31 +0200, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> On 15:03 Wed 01 Jun , Marc Zyngier wrote:
> > Currently, the boot CPU has its local timer enabled long after
> > the delay loop has been calibrated. This makes it impossible to
> > boot a system that only uses local timers, like the A15.
> >
> > Use late_time_init hook to initialize the boot CPU local timer.
> > Since shmobile is already using this hook, add an ARM specific
> > arm_late_time_init hook that platforms can use instead.
> >
> > Cc: Paul Mundt <lethal@linux-sh.org>
> > Cc: Magnus Damm <magnus.damm@gmail.com>
> > Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> I propose to switch to early platform devce and earlytimer
>
> this will avoid the arm_late_time_init hook
>
> and will make it cross arch
I believe this is orthogonal. shmobile (the only ARM user of
late_time_init) is already doing some early_platform stuff for its
timers.
What I'm trying to achieve here is to make sure the timer on CPU0 is
actually up, running and registered as a clock_event_device before we
hit the delay loop.
Or maybe I've misunderstood what you're pointing me to?
Cheers,
M.
--
Reality is an implementation detail.
next prev parent reply other threads:[~2011-06-02 16:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-01 14:03 [PATCH] ARM: local timers: Allow boot CPU to have its timer running early Marc Zyngier
2011-06-02 6:04 ` Paul Mundt
2011-06-02 16:31 ` Jean-Christophe PLAGNIOL-VILLARD
2011-06-02 16:56 ` Marc Zyngier [this message]
2011-06-02 19:38 ` Rob Herring
2011-06-03 8:20 ` Marc Zyngier
2011-06-03 8:55 ` Russell King - ARM Linux
2011-06-03 13:55 ` Rob Herring
2011-06-06 5:20 ` Magnus Damm
2011-06-03 8:57 ` Russell King - ARM Linux
2011-06-03 9:11 ` Marc Zyngier
2011-06-06 9:25 ` Paul Mundt
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=1307033815.31098.31.camel@e102391-lin.cambridge.arm.com \
--to=marc.zyngier@arm.com \
--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.