From: Kevin Hilman <khilman@mvista.com>
To: linux-omap-open-source@linux.omap.com
Subject: Re: [PATCH 0/3] 32k timer reorg
Date: Mon, 12 Nov 2007 12:00:16 -0800 [thread overview]
Message-ID: <1194897616.3334.6.camel@vence.hilman.org> (raw)
In-Reply-To: <20071112182209.262757465@mvista.com>
On Mon, 2007-11-12 at 10:22 -0800, Kevin Hilman wrote:
> Here's a short series of patches to reorganize and consolidate the 32k
> timer code. In particular, conslidate the usage of DM timers and move
> the OMAP1 specifics into mach-omap1.
I forgot to mention that this was tested on both OMAP1 (OSK) and OMAP2
(2430SDP) in both 32k and MPU timer mode.
Kevin
prev parent reply other threads:[~2007-11-12 20:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 18:22 [PATCH 0/3] 32k timer reorg Kevin Hilman
2007-11-12 18:22 ` [PATCH 1/3] ARM: OMAP: re-organize duplicated 32k-timer code Kevin Hilman
2007-11-12 18:22 ` [PATCH 2/3] ARM: OMAP: Move 32k-based sched_clock() to common code Kevin Hilman
2007-11-12 20:00 ` Kevin Hilman
2007-11-12 18:22 ` [PATCH 3/3] ARM: OMAP: Move timer32k to mach-omap1 Kevin Hilman
2007-11-12 20:00 ` Kevin Hilman [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=1194897616.3334.6.camel@vence.hilman.org \
--to=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