From: Viresh Kumar <viresh.kumar@linaro.org>
To: Thomas Gleixner <tglx@linutronix.de>,
Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>,
Andres Salomon <dilinger@queued.net>,
bcm-kernel-feedback-list@broadcom.com,
Florian Fainelli <f.fainelli@gmail.com>,
Lee Jones <lee@kernel.org>, Magnus Damm <magnus.damm@gmail.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Maxime Coquelin <maxime.coquelin@st.com>,
Patrice Chotard <patrice.chotard@st.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
Srinivas Kandagatla <srinivas.kandagatla@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: [PATCH V2 0/7] clockevent: Migrate to new 'set-state' interface
Date: Fri, 12 Jun 2015 13:30:10 +0530 [thread overview]
Message-ID: <cover.1434095303.git.viresh.kumar@linaro.org> (raw)
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 <dilinger@queued.net>
Cc: bcm-kernel-feedback-list@broadcom.com
Cc: Florian Fainelli <f.fainelli@gmail.com>
Cc: Lee Jones <lee@kernel.org>
Cc: Magnus Damm <magnus.damm@gmail.com>
Cc: Marc Zyngier <marc.zyngier@arm.com>
Cc: Maxime Coquelin <maxime.coquelin@st.com>
Cc: Patrice Chotard <patrice.chotard@st.com>
Cc: Ray Jui <rjui@broadcom.com>
Cc: Scott Branden <sbranden@broadcom.com>
Cc: Srinivas Kandagatla <srinivas.kandagatla@gmail.com>
Cc: Stephen Warren <swarren@wwwdotorg.org>
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
next reply other threads:[~2015-06-12 8:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 8:00 Viresh Kumar [this message]
2015-06-12 8:00 ` [PATCH V2 1/7] clockevents: Allow set-state callbacks to be optional Viresh Kumar
2015-06-29 8:47 ` Daniel Lezcano
2015-06-29 9:15 ` Thomas Gleixner
2015-06-12 8:00 ` [PATCH V2 2/7] clocksource: arm_arch_timer: Migrate to new 'set-state' interface Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 3/7] clocksource: arm_global_timer: " Viresh Kumar
2015-06-12 8:22 ` Maxime Coquelin
2015-06-12 8:28 ` Viresh Kumar
2015-06-12 9:10 ` srini
2015-06-12 9:11 ` Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 4/7] clocksource: bcm2835: " Viresh Kumar
2015-06-16 2:57 ` Stephen Warren
2015-06-16 3:17 ` Viresh Kumar
2015-06-16 4:16 ` Stephen Warren
2015-06-16 4:19 ` Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 5/7] clocksource: bcm_kona: " Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 6/7] clocksource: cs5535: " Viresh Kumar
2015-06-12 8:00 ` [PATCH V2 7/7] clocksource: em_sti: " Viresh Kumar
2015-06-18 9:10 ` [PATCH V2 0/7] clockevent: " Daniel Lezcano
2015-06-18 9:14 ` Daniel Lezcano
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=cover.1434095303.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.lezcano@linaro.org \
--cc=dilinger@queued.net \
--cc=f.fainelli@gmail.com \
--cc=lee@kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marc.zyngier@arm.com \
--cc=maxime.coquelin@st.com \
--cc=patrice.chotard@st.com \
--cc=rjui@broadcom.com \
--cc=sbranden@broadcom.com \
--cc=srinivas.kandagatla@gmail.com \
--cc=swarren@wwwdotorg.org \
--cc=tglx@linutronix.de \
/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