From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 1/4] clockevents: Add generic timer broadcast receiver
Date: Wed, 9 Jan 2013 14:46:07 +0000 [thread overview]
Message-ID: <1357742770-15028-2-git-send-email-mark.rutland@arm.com> (raw)
In-Reply-To: <1357742770-15028-1-git-send-email-mark.rutland@arm.com>
Currently the broadcast mechanism used for timers is abstracted by a
function pointer on struct clock_event_device. As the fundamental
mechanism for broadcast is architecture-specific, this ties each
clock_event_device driver to a single architecture, even where the
driver is otherwise generic.
This patch adds a standard path for the receipt of timer broadcasts, so
drivers and/or architecture backends need not manage redundant lists of
timers for the purpose of routing broadcast timer ticks.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Reviewed-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
Tested-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
---
include/linux/clockchips.h | 9 +++++++++
kernel/time/tick-broadcast.c | 12 ++++++++++++
2 files changed, 21 insertions(+), 0 deletions(-)
diff --git a/include/linux/clockchips.h b/include/linux/clockchips.h
index 8a7096f..6537114 100644
--- a/include/linux/clockchips.h
+++ b/include/linux/clockchips.h
@@ -161,6 +161,15 @@ clockevents_calc_mult_shift(struct clock_event_device *ce, u32 freq, u32 minsec)
extern void clockevents_suspend(void);
extern void clockevents_resume(void);
+#ifdef CONFIG_GENERIC_CLOCKEVENTS_BROADCAST
+extern int tick_receive_broadcast(void);
+#else
+static inline int tick_receive_broadcast(void)
+{
+ return 0;
+}
+#endif
+
#ifdef CONFIG_GENERIC_CLOCKEVENTS
extern void clockevents_notify(unsigned long reason, void *arg);
#else
diff --git a/kernel/time/tick-broadcast.c b/kernel/time/tick-broadcast.c
index f113755..5079bb7 100644
--- a/kernel/time/tick-broadcast.c
+++ b/kernel/time/tick-broadcast.c
@@ -125,6 +125,18 @@ int tick_device_uses_broadcast(struct clock_event_device *dev, int cpu)
return ret;
}
+int tick_receive_broadcast(void)
+{
+ struct tick_device *td = this_cpu_ptr(&tick_cpu_device);
+ struct clock_event_device *evt = td->evtdev;
+
+ if (!evt)
+ return -ENODEV;
+
+ evt->event_handler(evt);
+ return 0;
+}
+
/*
* Broadcast the event to the cpus, which are set in the mask (mangled).
*/
--
1.7.0.4
next prev parent reply other threads:[~2013-01-09 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 14:46 [PATCHv2 0/4] clockevents: decouple broadcast mechanism from drivers Mark Rutland
2013-01-09 14:46 ` Mark Rutland [this message]
2013-01-14 11:06 ` [PATCHv2 1/4] clockevents: Add generic timer broadcast receiver Thomas Gleixner
2013-01-14 11:29 ` Mark Rutland
2013-01-14 11:50 ` Thomas Gleixner
2013-01-14 12:12 ` Mark Rutland
2013-01-14 14:17 ` Thomas Gleixner
2013-01-14 15:36 ` Mark Rutland
2013-01-15 6:40 ` Santosh Shilimkar
2013-01-15 11:24 ` Thomas Gleixner
2013-01-15 12:00 ` Mark Rutland
2013-01-09 14:46 ` [PATCHv2 2/4] arm: Use " Mark Rutland
2013-01-09 14:46 ` [PATCHv2 3/4] clockevents: Add generic timer broadcast function Mark Rutland
2013-01-14 11:10 ` Thomas Gleixner
2013-01-09 14:46 ` [PATCHv2 4/4] arm: Add generic timer broadcast support Mark Rutland
2013-01-09 20:46 ` [PATCHv2 0/4] clockevents: decouple broadcast mechanism from drivers Stephen Boyd
2013-01-10 9:44 ` Mark Rutland
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=1357742770-15028-2-git-send-email-mark.rutland@arm.com \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).