From: plagnioj@jcrosoft.com (Jean-Christophe PLAGNIOL-VILLARD)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] clkdev: add support to lookup for early platform device
Date: Thu, 28 Apr 2011 13:19:17 +0200 [thread overview]
Message-ID: <20110428111917.GC31786@game.jcrosoft.org> (raw)
In-Reply-To: <20110428100719.GZ17290@n2100.arm.linux.org.uk>
On 11:07 Thu 28 Apr , Russell King - ARM Linux wrote:
> On Thu, Apr 28, 2011 at 11:26:13AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > On 09:35 Thu 28 Apr , Russell King - ARM Linux wrote:
> > > On Thu, Apr 28, 2011 at 07:12:03AM +0200, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > > How did you manage to get the clock for the earlytimer?
> > >
> > > This is getting silly. "Let's move all our devices to early" is insane.
> > > I can see someone then wanting an early-early-device because early has
> > > become just too late in the initialization.
> > >
> > > Come on guys, keep it simple and stop trying to contort the interfaces
> > > you're given into doing things they're not designed to do.
> > I agress but I need to pass resources to the timer so early devices make
> > sense
>
> Again, you shouldn't be setting up the timer at map_io time - the kernel
> just isn't ready for it.
>
> map_io is meant just for setting up IO mappings. You can then use the
> init_early callback to register tables, setting up sched_clock, getting
> the timer running for sched_clock, etc. At this point, memblock must not
> be used, but bootmem is active, but normal page allocation is not.
>
> The clocksource/clockevent initialization should happen after that when
> the system_timer->init function is called.
no the timer is init in the right place in system_timer->init
Best Regards,
J.
prev parent reply other threads:[~2011-04-28 11:19 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 14:05 [PATCH] clkdev: add support to lookup for early platform device Jean-Christophe PLAGNIOL-VILLARD
2011-04-27 8:42 ` Russell King - ARM Linux
2011-04-27 10:31 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-27 10:47 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-27 15:00 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-27 22:12 ` Greg KH
2011-04-28 2:09 ` Paul Mundt
2011-04-28 2:45 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:08 ` Paul Mundt
2011-04-28 3:17 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:20 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:35 ` Magnus Damm
2011-04-28 3:29 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:44 ` Magnus Damm
2011-04-28 8:33 ` Russell King - ARM Linux
2011-04-28 9:28 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 3:38 ` Paul Mundt
2011-04-28 4:31 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 4:46 ` Saravana Kannan
2011-04-28 4:50 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 5:12 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 5:47 ` Magnus Damm
2011-04-28 8:35 ` Russell King - ARM Linux
2011-04-28 9:26 ` Jean-Christophe PLAGNIOL-VILLARD
2011-04-28 10:07 ` Russell King - ARM Linux
2011-04-28 11:19 ` Jean-Christophe PLAGNIOL-VILLARD [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=20110428111917.GC31786@game.jcrosoft.org \
--to=plagnioj@jcrosoft.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.