From: Jamie Iles <jamie@jamieiles.com>
To: linux-kernel@vger.kernel.org
Cc: johnstul@us.ibm.com, tglx@linutronix.de,
jacob.jun.pan@linux.intel.com, Jamie Iles <jamie@jamieiles.com>
Subject: [RFC PATCH 0/2] Permit reuse of APB timers on other platforms
Date: Fri, 1 Apr 2011 12:08:09 +0100 [thread overview]
Message-ID: <1301656091-1284-1-git-send-email-jamie@jamieiles.com> (raw)
These patches allow the APB timers to be used by platforms other than
x86. The first patch moves the actual timer handling and
clocksource/clock_event_device abstraction into drivers/clocksource and
converts x86 to use this. The second patch adds a platform_driver to
allow other systems to use them.
I've tested these on an ARM platform with NO_HZ but I don't have an x86
platform with these timers that I can test them on so that's just
compile tested.
Jamie Iles (2):
x86, mrst: share APB timer code with other platforms
clocksource: platform driver for APB timers
arch/x86/Kconfig | 1 +
arch/x86/include/asm/apb_timer.h | 22 +--
arch/x86/kernel/apb_timer.c | 401 ++++-----------------------
drivers/Kconfig | 2 +
drivers/clocksource/Kconfig | 11 +
drivers/clocksource/Makefile | 2 +
drivers/clocksource/dw_apb_timer.c | 291 +++++++++++++++++++
drivers/clocksource/dw_apb_timer_platform.c | 173 ++++++++++++
include/linux/dw_apb_timer.h | 122 ++++++++
9 files changed, 662 insertions(+), 363 deletions(-)
create mode 100644 drivers/clocksource/Kconfig
create mode 100644 drivers/clocksource/dw_apb_timer.c
create mode 100644 drivers/clocksource/dw_apb_timer_platform.c
create mode 100644 include/linux/dw_apb_timer.h
--
1.7.4
next reply other threads:[~2011-04-01 11:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-01 11:08 Jamie Iles [this message]
2011-04-01 11:08 ` [RFC PATCH 1/2] x86, mrst: share APB timer code with " Jamie Iles
2011-04-01 11:08 ` [RFC PATCH 2/2] clocksource: platform driver for APB timers Jamie Iles
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=1301656091-1284-1-git-send-email-jamie@jamieiles.com \
--to=jamie@jamieiles.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®