From: Soren Brinkmann <soren.brinkmann@xilinx.com>
To: Rob Herring <rob.herring@calxeda.com>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Russell King <linux@arm.linux.org.uk>,
Michal Simek <michal.simek@xilinx.com>,
Thomas Gleixner <tglx@linutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Grant Likely <grant.likely@secretlab.ca>,
Preeti Murthy <preeti.lkml@gmail.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Soren Brinkmann <soren.brinkmann@xilinx.com>
Subject: [PATCH v2 0/4] arm: zynq: Enable global timer
Date: Wed, 18 Sep 2013 11:48:34 -0700 [thread overview]
Message-ID: <1379530118-22813-1-git-send-email-soren.brinkmann@xilinx.com> (raw)
Hi all,
here's a v2. I reused the subject from my v1 submission although the focus of
this series moved a bit towards the timer subsystem.
I replaced Stephen's fix to prevent per cpu devices from becoming
the broadcast device with Thomas' proposal, but I kept the original commit
message. I split the whole approach in small chunks that I found reasonable.
In 4/4, I picked up Grant's comment regarding the DT node name.
v2:
- drop 1/2 of the original series
- implement preventing per cpu devices from becoming broadcast device according
to Thomas' proposal
- introduce new CLOCK_EVT_FEAT_PERCPU flag
- set the flag for the arm_global_timer
- filter per cpu devices based on this flag when choosing the broadcast
device
- rename DT node to avoid '_'s
Soren Brinkmann (4):
clockchips: Add FEAT_PERCPU clockevent flag
clocksource/arm_global_timer: Set FEAT_PERCPU flag
tick: broadcast: Deny per-cpu clockevents from being broadcast sources
arm: zynq: Enable arm_global_timer
arch/arm/boot/dts/zynq-7000.dtsi | 8 ++++++++
arch/arm/mach-zynq/Kconfig | 1 +
drivers/clocksource/arm_global_timer.c | 3 ++-
include/linux/clockchips.h | 1 +
kernel/time/tick-broadcast.c | 1 +
5 files changed, 13 insertions(+), 1 deletion(-)
--
1.8.4
next reply other threads:[~2013-09-18 18:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-18 18:48 Soren Brinkmann [this message]
2013-09-18 18:48 ` [PATCH v2 1/4] clockchips: Add FEAT_PERCPU clockevent flag Soren Brinkmann
2013-09-25 15:10 ` Daniel Lezcano
2013-09-18 18:48 ` [PATCH v2 2/4] clocksource/arm_global_timer: Set FEAT_PERCPU flag Soren Brinkmann
2013-09-25 15:10 ` Daniel Lezcano
2013-09-26 10:38 ` Srinivas KANDAGATLA
2013-09-18 18:48 ` [PATCH v2 3/4] tick: broadcast: Deny per-cpu clockevents from being broadcast sources Soren Brinkmann
2013-09-25 15:11 ` Daniel Lezcano
2013-09-18 18:48 ` [PATCH v2 4/4] arm: zynq: Enable arm_global_timer Soren Brinkmann
2013-09-25 15:20 ` [PATCH v2 0/4] arm: zynq: Enable global timer Daniel Lezcano
2013-09-25 15:37 ` Sören Brinkmann
2013-09-26 8:16 ` Michal Simek
2013-09-26 10:14 ` Daniel Lezcano
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=1379530118-22813-1-git-send-email-soren.brinkmann@xilinx.com \
--to=soren.brinkmann@xilinx.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@secretlab.ca \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=pawel.moll@arm.com \
--cc=preeti.lkml@gmail.com \
--cc=rob.herring@calxeda.com \
--cc=sboyd@codeaurora.org \
--cc=swarren@wwwdotorg.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®