linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/5] Memory mapped architected timers
Date: Wed, 31 Jul 2013 15:38:33 -0700	[thread overview]
Message-ID: <20130731223833.GJ8868@codeaurora.org> (raw)
In-Reply-To: <20130724203253.GE27761@codeaurora.org>

On 07/24, Stephen Boyd wrote:
> On 07/22, Mark Rutland wrote:
> > 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.
> 
> Daniel, can you pick up these patches please?
> 

Ping Daniel?

-- 
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

  reply	other threads:[~2013-07-31 22:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-18 23:59 [PATCH v4 0/5] Memory mapped architected timers Stephen Boyd
2013-07-18 23:59 ` [PATCH v4 1/5] clocksource: arch_timer: Make register accessors less error-prone Stephen Boyd
2013-07-18 23:59 ` [PATCH v4 2/5] Documentation: Add memory mapped ARM architected timer binding Stephen Boyd
2013-07-18 23:59 ` [PATCH v4 3/5] clocksource: arch_timer: Pass clock event to set_mode callback Stephen Boyd
2013-07-18 23:59 ` [PATCH v4 4/5] clocksource: arch_timer: Push the read/write wrappers deeper Stephen Boyd
2013-07-18 23:59 ` [PATCH v4 5/5] clocksource: arch_timer: Add support for memory mapped timers Stephen Boyd
2013-07-22 17:08 ` [PATCH v4 0/5] Memory mapped architected timers Mark Rutland
2013-07-24 20:32   ` Stephen Boyd
2013-07-31 22:38     ` Stephen Boyd [this message]
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=20130731223833.GJ8868@codeaurora.org \
    --to=sboyd@codeaurora.org \
    --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).