From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/4] clockevents: decouple broadcast mechanism from drivers
Date: Wed, 9 Jan 2013 14:46:06 +0000 [thread overview]
Message-ID: <1357742770-15028-1-git-send-email-mark.rutland@arm.com> (raw)
This is an updated version of the series I posted back in December:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137929.html
Changes since v1:
* Drop removal of guards in smp.c
* Removed useless evt->evt_handler check in tick_receive_broadcast
* Fix up tick_receive_broadcast when !GENERIC_CLOCKEVENTS_BROADCAST
* Fix checkpatch issues (multi-line strings)
Thanks go to Stephen Boyd and Santosh Shilimkar for their commments.
In some SMP systems, cpu-local timers may stop delivering interrupts
when in low power states, or not all CPUs may have local timers. To
support these systems we have a mechanism for broadcasting timer ticks
to other CPUs. This mechanism relies on the struct
clock_event_device::broadcast function pointer, which is a
driver-specific mechanism for broadcasting ticks to other CPUs.
As the broadcast mechanism is architecture-specific, placing the
broadcast function on struct clock_event_device ties each driver to a
single architecture. Additionally the driver or architecture backend
must handle the routing of broadcast ticks to the correct
clock_event_device, leading to duplication of the list of active
clock_event_devices.
These patches introduce a generic mechanism for handling the receipt of
timer broadcasts, and an optional architecture-specific broadcast
function which allows drivers to be decoupled from a particular
architecture will retaining support for timer tick broadcasts. These
mechanisms are wired up for the arm port, and have been boot-tested on a
pandaboard.
Thanks,
Mark.
Mark Rutland (4):
clockevents: Add generic timer broadcast receiver
arm: Use generic timer broadcast receiver
clockevents: Add generic timer broadcast function
arm: Add generic timer broadcast support
arch/arm/Kconfig | 1 +
arch/arm/kernel/smp.c | 11 ++---------
include/linux/clockchips.h | 14 ++++++++++++++
kernel/time/Kconfig | 4 ++++
kernel/time/tick-broadcast.c | 25 +++++++++++++++++++++++++
5 files changed, 46 insertions(+), 9 deletions(-)
next 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 Mark Rutland [this message]
2013-01-09 14:46 ` [PATCHv2 1/4] clockevents: Add generic timer broadcast receiver Mark Rutland
2013-01-14 11:06 ` 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-1-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).