From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 06/10] arm: arch_timer: divorce from local_timer api
Date: Tue, 18 Dec 2012 12:20:16 +0000 [thread overview]
Message-ID: <20121218122002.GA29998@e106331-lin.cambridge.arm.com> (raw)
In-Reply-To: <20121210110754.GA18328@e106331-lin.cambridge.arm.com>
Stephen,
On Mon, Dec 10, 2012 at 11:09:41AM +0000, Mark Rutland wrote:
> On Fri, Dec 07, 2012 at 10:16:42PM +0000, Stephen Boyd wrote:
> > On 11/30/12 09:46, Mark Rutland wrote:
> > > Currently, the arch_timer driver is tied to the arm port, as it relies
> > > on code in arch/arm/smp.c to setup and teardown timers as cores are
> > > hotplugged on and off. The timer is registered through an arm-specific
> > > registration mechanism, preventing sharing the driver with the arm64
> > > port.
> > >
> > > This patch moves the driver to using a cpu notifier instead, making it
> > > easier to port.
> >
> > How does ipi_timer() work after this change? Don't we need it because of
> > FEAT_C3_STOP?
>
> The unfortunate answer is it doesn't, and we'll need broadcast for any systems
> where the timers turn off in low power states.
>
> I'll take a look at decoupling the broadcast mechanism from the drivers, it's
> not really a property of the clock hardware and it would be nice to split it.
I've had a go at splitting the broadcast mechanism in another series:
http://lists.infradead.org/pipermail/linux-arm-kernel/2012-December/137929.html
I'm evidently not proficient with git send-email -- I'd intended for you to be
on Cc.
Thanks,
Mark
next prev parent reply other threads:[~2012-12-18 12:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 17:45 [PATCH 00/10] Unify arm_generic and arch_timer drivers Mark Rutland
2012-11-30 17:45 ` [PATCH 01/10] arm: arch_timer: remove redundant available check Mark Rutland
2012-11-30 17:46 ` [PATCH 02/10] arm: arch_timer: use u64/u32 for register data Mark Rutland
2012-11-30 17:46 ` [PATCH 03/10] arm: arch_timer: standardise counter reading Mark Rutland
2012-11-30 17:46 ` [PATCH 04/10] arm: arch_timer: split cntfrq accessor Mark Rutland
2012-11-30 17:46 ` [PATCH 05/10] arm: arch_timer: factor out register accessors Mark Rutland
2012-11-30 17:46 ` [PATCH 06/10] arm: arch_timer: divorce from local_timer api Mark Rutland
2012-12-07 22:16 ` Stephen Boyd
2012-12-10 11:09 ` Mark Rutland
2012-12-18 12:20 ` Mark Rutland [this message]
2012-11-30 17:46 ` [PATCH 07/10] arm: arch_timer: add arch_counter_enable_user_access Mark Rutland
2012-11-30 19:32 ` Will Deacon
2012-12-03 10:24 ` Mark Rutland
2012-11-30 17:46 ` [PATCH 08/10] arm: arch_timer: move core to drivers/clocksource Mark Rutland
2012-11-30 17:46 ` [PATCH 09/10] arm64: move from arm_generic to arm_arch_timer Mark Rutland
2012-11-30 19:36 ` Will Deacon
2012-11-30 17:46 ` [PATCH 10/10] Documentation: Add ARMv8 to arch_timer devicetree 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=20121218122002.GA29998@e106331-lin.cambridge.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).