[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140207075618.17187.20149.stgit@preeti.in.ibm.com>
Date: Fri, 07 Feb 2014 13:35:56 +0530
From: Preeti U Murthy <preeti@...ux.vnet.ibm.com>
To: linux-pm@...r.kernel.org, peterz@...radead.org,
benh@...nel.crashing.org, rafael.j.wysocki@...el.com,
linux-kernel@...r.kernel.org, tglx@...utronix.de,
linuxppc-dev@...ts.ozlabs.org, mingo@...nel.org
Cc: deepthi@...ux.vnet.ibm.com, paulmck@...ux.vnet.ibm.com,
fweisbec@...il.com, paulus@...ba.org,
srivatsa.bhat@...ux.vnet.ibm.com, svaidy@...ux.vnet.ibm.com
Subject: [PATCH V4 0/3] time/cpuidle: Support in tick broadcast framework in
absence of external clock device
This patchset provides support in the tick broadcast framework for such
architectures so as to enable the CPUs to get into deep idle.
Presently we are in need of this support on certain implementations of
PowerPC. This patchset has thus been tested on the same.
This patchset has been based on the idea discussed here:
http://www.kernelhub.org/?p=2&msg=399516
Changes in V4:
1. Cleared the stand by CPU from the oneshot mask. As a result PATCH 3/3
was simplified.
2. Fixed compile time warnings.
---
Preeti U Murthy (2):
time: Change the return type of clockevents_notify() to integer
time/cpuidle:Handle failed call to BROADCAST_ENTER on archs with CPUIDLE_FLAG_TIMER_STOP set
Thomas Gleixner (1):
tick/cpuidle: Initialize hrtimer mode of broadcast
drivers/cpuidle/cpuidle.c | 14 +++--
include/linux/clockchips.h | 15 ++++-
kernel/time/Makefile | 2 -
kernel/time/clockevents.c | 8 ++-
kernel/time/tick-broadcast-hrtimer.c | 105 ++++++++++++++++++++++++++++++++++
kernel/time/tick-broadcast.c | 60 ++++++++++++++++++-
kernel/time/tick-internal.h | 6 +-
7 files changed, 189 insertions(+), 21 deletions(-)
create mode 100644 kernel/time/tick-broadcast-hrtimer.c
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists