All of lore.kernel.org
 help / color / mirror / Atom feed
From: lethal@linux-sh.org (Paul Mundt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: local timers: Allow boot CPU to have its timer running early
Date: Mon, 6 Jun 2011 18:25:36 +0900	[thread overview]
Message-ID: <20110606092535.GA30400@linux-sh.org> (raw)
In-Reply-To: <20110603085735.GH10532@n2100.arm.linux.org.uk>

On Fri, Jun 03, 2011 at 09:57:35AM +0100, Russell King - ARM Linux wrote:
> On Wed, Jun 01, 2011 at 03:03:26PM +0100, 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.
> 
> Why do we need to initialize the per-cpu timer in late_time_init() ?
> Is there a reason it doesn't work at time_init(), and if not can it
> be fixed to work there?

There are a number of ordering issues. It's necessary to have the clock
framework and everything else initialized before the per-cpu timer can
come up. While we did originally have this at the end of the time_init()
path there were some interactivity issues with regards to lockdep and
having IRQs initialized too early, which was the principle rationale for
deferring it.

      parent reply	other threads:[~2011-06-06  9:25 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
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 [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=20110606092535.GA30400@linux-sh.org \
    --to=lethal@linux-sh.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.