From: Mark Rutland <mark.rutland@arm.com>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Daniel Lezcano <daniel.lezcano@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
Marc Zyngier <Marc.Zyngier@arm.com>,
Rob Herring <robherring2@gmail.com>
Subject: Re: [PATCH v4 0/5] Memory mapped architected timers
Date: Mon, 22 Jul 2013 18:08:17 +0100 [thread overview]
Message-ID: <20130722170817.GB4833@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <1374191972-18015-1-git-send-email-sboyd@codeaurora.org>
Hi Stephen,
On Fri, Jul 19, 2013 at 12:59:27AM +0100, Stephen Boyd wrote:
> This patchset adds support for memory mapped architected timers. We
> don't have any other global broadcast timer in our system, so we use the
> mmio timer during low power modes. The first patch changes the register
> accessor to an enum per Thomas' request. The second patch is the binding.
> The next two patches lay some groundwork so that the last patch is simpler.
> The final patch adds support for mmio timers.
>
> Patches are based on v3.11-rc1.
Be aware that as of v3.11-rc2 this doesn't cleanly apply, as the
__cpuinit removal broke the final patch's context in a couple of places.
It would be nice to get rid of the new cpuinit additions too...
With that cleaned up locally, I've gave this a spin on tc2 and a
Foundation model to test the cp15/system timers, hotplugging CPUs and
running a basic test (`time sleep 5`). That all seems to work.
Unfortunately I have no way of testing the memory-mapped timer support,
but I trust you've tested that locally.
For the series:
Acked-by: Mark Rutland <mark.rutland@arm.com>
Thanks,
Mark.
>
> Updates since v3:
> * Rebased onto v3.11-rc1
> * New patch to use compiler warnings instead of BUILD_BUG_ON()
>
> Updates since v2:
> * Rebased onto v3.10-rc1
>
> Updates since v1:
> * Assigned counter reading function and commented why for arm64
> * Updated DT binding to replace frame-id with frame-number and use status
> property
>
>
> Stephen Boyd (5):
> clocksource: arch_timer: Make register accessors less error-prone
> Documentation: Add memory mapped ARM architected timer binding
> clocksource: arch_timer: Pass clock event to set_mode callback
> clocksource: arch_timer: Push the read/write wrappers deeper
> clocksource: arch_timer: Add support for memory mapped timers
>
> .../devicetree/bindings/arm/arch_timer.txt | 59 ++-
> arch/arm/include/asm/arch_timer.h | 14 +-
> arch/arm64/include/asm/arch_timer.h | 23 +-
> drivers/clocksource/arm_arch_timer.c | 446 +++++++++++++++++----
> include/clocksource/arm_arch_timer.h | 10 +-
> 5 files changed, 455 insertions(+), 97 deletions(-)
>
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> hosted by The Linux Foundation
>
>
next prev parent reply other threads:[~2013-07-22 17:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 23:59 [PATCH v4 0/5] Memory mapped architected timers Stephen Boyd
[not found] ` <1374191972-18015-1-git-send-email-sboyd-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2013-07-18 23:59 ` [PATCH v4 2/5] Documentation: Add memory mapped ARM architected timer binding Stephen Boyd
2013-07-22 17:08 ` Mark Rutland [this message]
2013-07-24 20:32 ` [PATCH v4 0/5] Memory mapped architected timers Stephen Boyd
2013-07-31 22:38 ` Stephen Boyd
2013-07-31 22:49 ` Daniel Lezcano
2013-07-31 23:16 ` 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=20130722170817.GB4833@e106331-lin.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robherring2@gmail.com \
--cc=sboyd@codeaurora.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;
as well as URLs for NNTP newsgroup(s).