From: Russell King <rmk@arm.linux.org.uk>
To: Paul Walmsley <paul@pwsan.com>
Cc: Aaro Koskinen <aaro.koskinen@nokia.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>,
Tony Lindgren <tony@atomide.com>,
linux-omap@vger.kernel.org
Subject: Re: Open issues after 2.6.38 merge window
Date: Mon, 17 Jan 2011 20:39:02 +0000 [thread overview]
Message-ID: <20110117203902.GC4042@flint.arm.linux.org.uk> (raw)
In-Reply-To: <alpine.DEB.2.00.1101171319590.13225@utopia.booyaka.com>
On Mon, Jan 17, 2011 at 01:31:47PM -0700, Paul Walmsley wrote:
> On Mon, 17 Jan 2011, Aaro Koskinen wrote:
>
> > On Mon, 17 Jan 2011, Santosh Shilimkar wrote:
> > > > Amstrad E3 fails during the boot. Bisection points to:
> > > >
> > > > commit 211baa7016894c02fc18693e21ca479cd08ac0c0
> > > > Author: Russell King <rmk+kernel@arm.linux.org.uk>
> > > > Date: Tue Jan 11 16:23:04 2011 +0000
> > > >
> > > > ARM: sched_clock: allow init_sched_clock() to be called
> > > > early
> > > >
> > > > The board does not have sched_clock(), although HAVE_SCHED_CLOCK is
> > > > defined for all OMAP.
> > > >
> > > I guess above is sorted out by the attached patch from Paul.
> >
> > I don't see how it could help? Amstrad E3 is OMAP 15xx.
>
> OMAP15xx uses the MPU timer for its clocksource, since OMAP15xx doesn't
> have GPTIMERs or the 32k sync timer, and the MPU timer code in
> mach-omap1/time.c wasn't updated for sched_clock() support.
>
> Adding an init_fixed_sched_clock() into omap_init_clocksource() should
> fix the boot on OMAP15xx/7xx.
No, it needs fixing properly. There's no reason the gpt clocksource
can't be used for sched_clock. We just need to switch to the variable
rate implementation rather than the fixed rate if we include OMAP15xx/7xx
support.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2011-01-17 20:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 19:47 Open issues after 2.6.38 merge window Tony Lindgren
2011-01-14 20:24 ` Tony Lindgren
2011-01-14 20:37 ` Jarkko Nikula
2011-01-14 20:54 ` Tony Lindgren
2011-01-14 22:22 ` Nishanth Menon
2011-01-14 20:57 ` David Anders
2011-01-14 23:38 ` Tony Lindgren
2011-01-14 23:59 ` Tony Lindgren
2011-01-14 23:54 ` Thomas Weber
2011-01-15 5:19 ` Santosh Shilimkar
2011-01-17 10:15 ` Santosh Shilimkar
2011-01-27 18:41 ` Tony Lindgren
2011-01-17 11:37 ` Aaro Koskinen
2011-01-17 11:59 ` Santosh Shilimkar
2011-01-17 12:11 ` Russell King
2011-01-17 12:19 ` Santosh Shilimkar
2011-01-17 12:24 ` Russell King
2011-01-17 18:29 ` Tony Lindgren
2011-01-17 12:22 ` Aaro Koskinen
2011-01-17 12:35 ` Santosh Shilimkar
2011-01-17 12:50 ` Russell King
2011-01-17 18:20 ` Tony Lindgren
2011-01-17 20:31 ` Paul Walmsley
2011-01-17 20:39 ` Russell King [this message]
2011-01-17 21:00 ` Paul Walmsley
2011-01-17 21:19 ` Russell King
2011-01-17 22:49 ` Paul Walmsley
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=20110117203902.GC4042@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=aaro.koskinen@nokia.com \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.com \
/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.