From: Dirk Behme <dirk.behme@googlemail.com>
To: Kevin Hilman <khilman@mvista.com>,
OMAP-Linux <linux-omap-open-source@linux.omap.com>
Subject: Re: [RFC] [PATCH] ARM: OMAP1: Add clocksource driver for OMAP1
Date: Wed, 08 Nov 2006 17:44:34 +0100 [thread overview]
Message-ID: <45520972.7060805@gmail.com> (raw)
In-Reply-To: <4550CA9E.6090500@mvista.com>
Kevin Hilman wrote:
> Dirk Behme wrote:
>>Add clocksource driver for OMAP1.
>>
>>Signed-off-by: Dirk Behme <dirk.behme_at_gmail.com>
>>
>>What do you think about this? OSK still boots and I can't
>>see any runtime issues. But maybe others?
>
> Daniel Walker and myself have done both the clocksource and clockevent
> drivers for the 32k timer and MPU timers on OMAP1.
Ah, thanks for the hint! I overlooked [1].
> The clocksource driver has been submitted to RMK's patchsystem (but not
> yet integrated, RMK is waiting some settling in mainline too)
http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=3876/1
- For clocksource_mpu.mult and clocksource_register stuff we
should (later?) have a seperate function
omap_init_clocksource() to be able to call it by something like
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2006-October/036700.html
- While working on same topic I wonder if we still need both
HW timers in timer.c
setup_irq(INT_TIMER1, &omap_mpu_timer1_irq);
setup_irq(INT_TIMER2, &omap_mpu_timer_irq);
omap_mpu_timer_start(0, 0xffffffff);
omap_mpu_timer_start(1, MPU_TIMER_TICK_PERIOD);
?
My test worked with using only one HW timer and removing all
other stuff:
setup_irq(INT_TIMER1, &omap_mpu_timer_irq);
omap_mpu_timer_start(0, MPU_TIMER_TICK_PERIOD);
But maybe I missed anything?
> and the
> rest has been submitted to Thomas Gliexner and will be included in his
> next -hrt-dyntick patcheset[2]
>
> The active -hrt-dyntick work is going on in -mm right now. The attached
> patchset (against 2.6.19-rc2-mm2) includes the latest OMAP patches which
> will be part of the next -hrt-dyntick patchset.
I think OMAP in mainline is slightly different from our git
tree here. Some parts are missing in mainline. If mainline
has merged everything and we pull it back to our OMAP git,
do we need a patch to adapt OMAP stuff not in mainline yet
to changes for -hrt-dyntick?
See RT preemt: If you try to apply RT preemt 2.6.18-rt7
(which is against OMAP in mainline) to OMAP 2.6.18 git, it
doesn't apply cleanly. Parts are missing and different
between OMAP git and OMAP mainline.
> We've tested these with Ingo's -rt patchset on 16xx/H2 and 1710/H3 and
> see good performance. We've also validated the new generic dynamic tick
> support which is part of the -hrt-dyntick patchset
Full text untouched here because seems that large attachment
prevented it from keeping in list archive.
> [2] http://tglx.de/projects/hrtimers/
Cheers,
Dirk
[1]
http://linux.omap.com/pipermail/linux-omap-open-source/2006-September/008008.html
next prev parent reply other threads:[~2006-11-08 16:44 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-07 15:32 [RFC] [PATCH] ARM: OMAP1: Add clocksource driver for OMAP1 Dirk Behme
[not found] ` <4550CA9E.6090500@mvista.com>
2006-11-08 16:44 ` Dirk Behme [this message]
2006-11-10 0:29 ` Tony Lindgren
2006-11-10 0:48 ` Kevin Hilman
2006-11-10 0:53 ` Tony Lindgren
2006-11-30 19:57 ` Woodruff, Richard
2006-11-30 21:30 ` David Brownell
2006-11-30 21:49 ` Woodruff, Richard
2006-11-30 22:32 ` David Brownell
2006-11-30 22:57 ` Woodruff, Richard
2006-11-30 22:12 ` tony
2006-11-30 21:59 ` tony
2006-11-30 22:24 ` Woodruff, Richard
2006-11-30 22:37 ` tony
2006-11-30 17:55 ` Dirk Behme
2006-11-30 17:50 ` Daniel Walker
2006-12-01 16:12 ` Dirk Behme
2006-12-02 3:21 ` Daniel Walker
2006-12-02 6:11 ` Dirk Behme
2006-12-02 6:54 ` Daniel Walker
2006-12-02 7:06 ` Dirk Behme
2006-12-02 7:18 ` Daniel Walker
2006-12-04 23:34 ` Kevin Hilman
2006-11-30 19:14 ` David Brownell
2006-11-30 20:33 ` Dirk Behme
2006-11-30 21:22 ` [RFC] [PATCH] ARM: Add clocksource driver for OMAP1 and OMAP2 David Brownell
2006-12-01 18:21 ` Dirk Behme
2006-12-01 19:03 ` David Brownell
2006-12-01 22:13 ` Tony Lindgren
2006-12-03 2:58 ` David Brownell
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=45520972.7060805@gmail.com \
--to=dirk.behme@googlemail.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