From: Sudeep KarkadaNagesha <sudeep.karkadanage...@arm.com> This patch series adds support to configure the rate and enable the event stream for architected timer. The event streams can be used to impose a timeout on a WFE, to safeguard against any programming error in case an expected event is not generated or even to implement wfe-based timeouts for userspace locking implementations.
Since the timer control register is reset to zero on warm boot, CPU PM notifier is added to re-initialize it. Changes v2->v3: 1. Moved ARM and ARM64 changes into separate patches 2. Added native hwcaps definations(ARM/ARM64) and compat-specific definitions(ARM64) to the users for the event stream feature. Changes v1->v2: 1. Saved event stream divider value on cold reset path and re-used it in CPU PM notifier instead of calculating every time. 2. Rebased on v3.11-rc2(to avoid conflicts with __cpuinit* deletion) 3. Dropped "ARM/ARM64: arch_timer: remove __cpuinit attribute for arch_counter_set_user_access"(already done as part of __cpuinit* deletion) Regards, Sudeep Sudeep KarkadaNagesha (5): ARM/ARM64: arch_timer: add macros for bits in control register ARM: arch_timer: configure and enable event stream ARM64: arch_timer: configure and enable event stream drivers: clocksource: enable hwcaps for event stream on ARM arch timer drivers: clocksource: add CPU PM notifier for ARM architected timer Will Deacon (1): drivers: clocksource: configure event stream for ARM arch timer arch/arm/include/asm/arch_timer.h | 18 +++++++++++--- arch/arm/include/uapi/asm/hwcap.h | 1 + arch/arm/kernel/setup.c | 1 + arch/arm64/include/asm/arch_timer.h | 22 +++++++++++++---- arch/arm64/include/asm/hwcap.h | 4 ++- arch/arm64/include/uapi/asm/hwcap.h | 1 + arch/arm64/kernel/setup.c | 1 + drivers/clocksource/arm_arch_timer.c | 48 +++++++++++++++++++++++++++++++++++- include/clocksource/arm_arch_timer.h | 10 ++++++++ 9 files changed, 96 insertions(+), 10 deletions(-) -- 1.8.1.2 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
