From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv4 00/11] Remove ARM local timer API
Date: Wed, 17 Apr 2013 13:44:26 -0700 [thread overview]
Message-ID: <516F09AA.2000902@codeaurora.org> (raw)
In-Reply-To: <1365456453-16297-1-git-send-email-sboyd@codeaurora.org>
Thomas,
Would you be able to pick up patches 1 and 2 from this series and
publish it as a stable branch? Preferably based on rc5 but I can always
merge it to rc5 and apply the rest of the patches.
Arnd/Olof,
Would you be able to merge in the rest of the patches to arm-soc? I can
provide a branch on 3.9-rc5 and a merge resolution with for-next in
arm-soc that you can pull to look at.
If not I will have to resend the series.
Thanks,
Stephen
On 04/08/13 14:27, Stephen Boyd wrote:
> In light of Mark Rutland's recent work on divorcing the ARM architected
> timers from the ARM local timer API and introducing a generic arch hook for
> broadcast it seems that we should remove the local timer API entirely.
> Doing so will reduce the architecture dependencies of our timer drivers,
> reduce code in ARM core, and simplify timer drivers because they no longer
> go through an architecture layer that is essentially a hotplug notifier.
>
> Previous attempts have been made[1] unsuccessfully. I'm hoping this can
> be accepted now so that we can clean up the timer drivers that are
> used in both UP and SMP situations. Right now these drivers have to ignore
> the timer setup callback on the boot CPU to avoid registering clockevents
> twice. This is not very symmetric and causes convuluted code that does
> the same thing in two places.
>
> Patches based on v3.9-rc5. I'm still looking for Acks/Tested-by
> on EXYNOS and PRIMA2.
>
> [1] http://article.gmane.org/gmane.linux.ports.arm.kernel/145705
>
> Note: A hotplug notifier is used by both x86 for the apb_timer (see
> apbt_cpuhp_notify) and by metag (see arch_timer_cpu_notify in
> metag_generic.c) so this is not new.
>
> Changes since v3:
> * New patch to fix SMP with dummy timers registered after a global timer
> * Push this_cpu_ptr lower to avoid preemptible false positive warnings
> * Collected acks/tested-bys
>
> Changes since v2:
> * Bug fixes in smp_twd from Tony Lindgren's testing
> * Move smp_twd to use late_time_init hook
> * Collected Acks
>
> Changes since v1:
> * Picked up Mark's generic dummy timer driver
> * Split out omap changes into new patch
>
> Mark Rutland (1):
> clocksource: add generic dummy timer driver
>
> Stephen Boyd (10):
> clockevents: Prefer CPU local devices over global devices
> ARM: smp: Remove duplicate dummy timer implementation
> ARM: smp_twd: Divorce smp_twd from local timer API
> ARM: OMAP2+: Divorce from local timer API
> ARM: EXYNOS4: Divorce mct from local timer API
> ARM: PRIMA2: Divorce timer-marco from local timer API
> ARM: msm: Divorce msm_timer from local timer API
> clocksource: time-armada-370-xp: Fix sparse warning
> clocksource: time-armada-370-xp: Divorce from local timer API
> ARM: smp: Remove local timer API
>
> arch/arm/Kconfig | 12 +--
> arch/arm/include/asm/localtimer.h | 34 ---------
> arch/arm/kernel/smp.c | 87 ---------------------
> arch/arm/kernel/smp_twd.c | 64 +++++++++++-----
> arch/arm/mach-exynos/mct.c | 60 ++++++++++-----
> arch/arm/mach-msm/timer.c | 127 +++++++++++++++++--------------
> arch/arm/mach-omap2/Kconfig | 1 -
> arch/arm/mach-omap2/timer.c | 7 --
> arch/arm/mach-prima2/timer-marco.c | 100 +++++++++++++-----------
> drivers/clocksource/Makefile | 1 +
> drivers/clocksource/dummy_timer.c | 69 +++++++++++++++++
> drivers/clocksource/time-armada-370-xp.c | 92 +++++++++++-----------
> include/linux/time-armada-370-xp.h | 4 +-
> kernel/time/tick-common.c | 5 +-
> 14 files changed, 327 insertions(+), 336 deletions(-)
> delete mode 100644 arch/arm/include/asm/localtimer.h
> create mode 100644 drivers/clocksource/dummy_timer.c
>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-04-17 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 21:27 [PATCHv4 00/11] Remove ARM local timer API Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 01/11] clockevents: Prefer CPU local devices over global devices Stephen Boyd
2013-04-09 10:33 ` Mark Rutland
2013-04-09 16:49 ` Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 02/11] clocksource: add generic dummy timer driver Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 03/11] ARM: smp: Remove duplicate dummy timer implementation Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 04/11] ARM: smp_twd: Divorce smp_twd from local timer API Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 05/11] ARM: OMAP2+: Divorce " Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 06/11] ARM: EXYNOS4: Divorce mct " Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 07/11] ARM: PRIMA2: Divorce timer-marco " Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 08/11] ARM: msm: Divorce msm_timer " Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 09/11] clocksource: time-armada-370-xp: Fix sparse warning Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 10/11] clocksource: time-armada-370-xp: Divorce from local timer API Stephen Boyd
2013-04-08 21:27 ` [PATCHv4 11/11] ARM: smp: Remove " Stephen Boyd
2013-04-17 20:44 ` Stephen Boyd [this message]
2013-04-18 16:39 ` [PATCHv4 00/11] Remove ARM " Olof Johansson
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=516F09AA.2000902@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).