Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754759AbbFLIAf (ORCPT ); Fri, 12 Jun 2015 04:00:35 -0400 Received: from mail-pd0-f176.google.com ([209.85.192.176]:34352 "EHLO mail-pd0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751163AbbFLIAc (ORCPT ); Fri, 12 Jun 2015 04:00:32 -0400 From: Viresh Kumar To: Thomas Gleixner , Daniel Lezcano Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org, Viresh Kumar , Andres Salomon , bcm-kernel-feedback-list@broadcom.com, Florian Fainelli , Lee Jones , Magnus Damm , Marc Zyngier , Maxime Coquelin , Patrice Chotard , Ray Jui , Scott Branden , Srinivas Kandagatla , Stephen Warren Subject: [PATCH V2 0/7] clockevent: Migrate to new 'set-state' interface Date: Fri, 12 Jun 2015 13:30:10 +0530 Message-Id: X-Mailer: git-send-email 2.4.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3157 Lines: 77 Hi Thomas/Daniel, I have incorporated all the improvements Daniel suggested on V1 and so here is V2. The first patch allows set-state callbacks to be optional, otherwise it leads to unnecessary noop callbacks for drivers which don't want to implement them. Over that, these noop-callbacks result in full function calls for nothing really useful. Rest of the series converts few clockevent drivers to the new set-state interface. This would enable these drivers to use new states (like: ONESHOT_STOPPED, etc.) of a clockevent device (if required), as the set-mode interface is marked obsolete now and wouldn't be expanded to handle new states. Once all the drivers are migrated to the new interface in future, we can remove the code supporting '->mode' in clockevents core. Drivers converted in this series are selected based on the diff they generate. These are different diffs we shall have for most of the drivers and any suggestions/improvements for these patches will be applied to other drivers as well. This is based of latest tip/master from few days back due to dependency on clockevent_state_*() helpers. Only the first patch is tested on hardware, others are ONLY compile tested. V1->V2: - New commit: 1/7 (Daniel) - Added all Acks from Daniel - Updated 2/7 to return 0 directly from timer_shutdown() - Naming fixes suggested for kona driver (Ray Jui) - Minor changes in commit logs - Not adding noop-callbacks Cc: Andres Salomon Cc: bcm-kernel-feedback-list@broadcom.com Cc: Florian Fainelli Cc: Lee Jones Cc: Magnus Damm Cc: Marc Zyngier Cc: Maxime Coquelin Cc: Patrice Chotard Cc: Ray Jui Cc: Scott Branden Cc: Srinivas Kandagatla Cc: Stephen Warren Viresh Kumar (7): clockevents: Allow set-state callbacks to be optional clocksource: arm_arch_timer: Migrate to new 'set-state' interface clocksource: arm_global_timer: Migrate to new 'set-state' interface clocksource: bcm2835: Migrate to new 'set-state' interface clocksource: bcm_kona: Migrate to new 'set-state' interface clocksource: cs5535: Migrate to new 'set-state' interface clocksource: em_sti: Migrate to new 'set-state' interface drivers/clocksource/arm_arch_timer.c | 52 ++++++++++++++-------------------- drivers/clocksource/arm_global_timer.c | 37 +++++++++++------------- drivers/clocksource/bcm2835_timer.c | 16 ----------- drivers/clocksource/bcm_kona_timer.c | 17 ++++------- drivers/clocksource/cs5535-clockevt.c | 24 +++++++++------- drivers/clocksource/em_sti.c | 39 +++++++++---------------- kernel/time/clockevents.c | 24 ++++++---------- 7 files changed, 81 insertions(+), 128 deletions(-) -- 2.4.0 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/