From: Tony Lindgren <tony@atomide.com>
To: Kevin Hilman <khilman@mvista.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 3/4] ARM: OMAP: Remove MPU-timer based sched_clock()
Date: Mon, 26 Nov 2007 10:40:04 -0800 [thread overview]
Message-ID: <20071126184004.GC21886@atomide.com> (raw)
In-Reply-To: <1196092764.8693.10.camel@vence.hilman.org>
* Kevin Hilman <khilman@mvista.com> [071126 07:59]:
>
> On Fri, 2007-11-23 at 11:18 -0800, Tony Lindgren wrote:
> > * Kevin Hilman <khilman@mvista.com> [071112 15:25]:
> > > Remove MPU-timer based sched_clock() in favor of the common one based
> > > on 32k sync timer which works across all OMAP1/2/3 platforms.
> > >
> > > Using 32k based one also gives a valid sched_clock() very early in the
> > > boot process.
> >
> > AFAIK there is no 32k sync timer for 15xx, or have I missed something?
> >
>
> No there isn't.
>
> But all this means is that 15xx has no higher resolution sched_clock().
> The ARM default jiffies-based one will be used.
I guess I don't understand what you're after by not using mpu timer 2
for proper sched_clock, some PM issues?
Maybe for PM reasons not having mpu timer 2 running could make sense if
it blocks some sleep states. But then again there's no timesource during
sleep states unless mpu timer 2 can use the 32K clock as a source clock..
Tony
next prev parent reply other threads:[~2007-11-26 18:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 23:24 [PATCH 0/4] 32k timer reorg and sched_clock cleanup Kevin Hilman
2007-11-12 23:24 ` [PATCH 1/4] ARM: OMAP: re-organize duplicated 32k-timer code Kevin Hilman
2007-11-12 23:24 ` [PATCH 2/4] ARM: OMAP: Move 32k-based sched_clock() to common code Kevin Hilman
2007-11-12 23:24 ` [PATCH 3/4] ARM: OMAP: Remove MPU-timer based sched_clock() Kevin Hilman
2007-11-23 19:18 ` Tony Lindgren
2007-11-23 20:26 ` Tony Lindgren
2007-11-26 15:59 ` Kevin Hilman
2007-11-26 18:40 ` Tony Lindgren [this message]
2007-11-26 19:30 ` Kevin Hilman
2007-11-26 20:12 ` Tony Lindgren
2007-11-12 23:24 ` [PATCH 4/4] ARM: OMAP: Move timer32k to mach-omap1 Kevin Hilman
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=20071126184004.GC21886@atomide.com \
--to=tony@atomide.com \
--cc=khilman@mvista.com \
--cc=linux-omap-open-source@linux.omap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox