From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 1/7] clockevents: Allow set-state callbacks to be optional
Date: Mon, 29 Jun 2015 10:47:27 +0200 [thread overview]
Message-ID: <5591061F.9040008@linaro.org> (raw)
In-Reply-To: <2e6dadb011755d94fa88482e67641c7d9dfff67d.1434095303.git.viresh.kumar@linaro.org>
On 06/12/2015 10:00 AM, Viresh Kumar wrote:
> Its mandatory for the drivers to provide set_state_{oneshot|periodic}()
> (only if related modes are supported) and set_state_shutdown() callbacks
> today, if they are implementing the new set-state interface.
>
> But this leads to unnecessary noop callbacks for drivers which don't
> want to implement them. Over that, it will lead to a full function call
> for nothing really useful.
>
> Lets make all set-state callbacks optional.
>
> Suggested-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
As this patch is needed for the other changes in this patchset, is it
possible to take it through my tree Thomas ?
--
<http://www.linaro.org/> Linaro.org │ Open source software for ARM SoCs
Follow Linaro: <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog
next prev parent reply other threads:[~2015-06-29 8:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-12 8:00 [PATCH V2 0/7] clockevent: Migrate to new 'set-state' interface Viresh Kumar
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 [this message]
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=5591061F.9040008@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=viresh.kumar@linaro.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