From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] clockevent: Migrate to new 'set-state' interface
Date: Thu, 11 Jun 2015 14:08:56 +0200 [thread overview]
Message-ID: <55797A58.9020601@linaro.org> (raw)
In-Reply-To: <cover.1433768426.git.viresh.kumar@linaro.org>
On 06/08/2015 03:40 PM, Viresh Kumar wrote:
> Hi Thomas/Daniel,
>
> This 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 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.
I suggest you use the kernel continuous integration [1] to test the
patches, it is probable some of the hardware is there.
-- Daniel
[1] http://kernelci.org/
--
<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-11 12:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 13:40 [PATCH 0/6] clockevent: Migrate to new 'set-state' interface Viresh Kumar
2015-06-08 13:40 ` [PATCH 1/6] clocksource: arm_arch_timer: " Viresh Kumar
2015-06-11 12:23 ` Daniel Lezcano
2015-06-11 12:57 ` Viresh Kumar
2015-06-08 13:40 ` [PATCH 2/6] clocksource: arm_global_timer: " Viresh Kumar
2015-06-11 14:49 ` Daniel Lezcano
2015-06-11 14:56 ` Viresh Kumar
2015-06-11 14:58 ` Daniel Lezcano
2015-06-12 8:39 ` Srinivas Kandagatla
2015-06-12 8:51 ` Viresh Kumar
2015-06-08 13:40 ` [PATCH 3/6] clocksource: bcm2835: " Viresh Kumar
2015-06-11 15:25 ` Daniel Lezcano
2015-06-11 16:00 ` Viresh Kumar
2015-06-11 16:13 ` Daniel Lezcano
2015-06-11 16:27 ` Viresh Kumar
2015-06-08 13:40 ` [PATCH 4/6] clocksource: bcm_kona: " Viresh Kumar
2015-06-08 16:09 ` Ray Jui
2015-06-08 16:22 ` Viresh Kumar
2015-06-08 16:30 ` Ray Jui
2015-06-08 17:10 ` Ray Jui
2015-06-08 13:40 ` [PATCH 5/6] clocksource: cs5535: " Viresh Kumar
2015-06-11 15:50 ` Daniel Lezcano
2015-06-08 13:40 ` [PATCH 6/6] clocksource: em_sti: " Viresh Kumar
2015-06-11 15:53 ` Daniel Lezcano
2015-06-11 12:08 ` Daniel Lezcano [this message]
2015-06-11 13:00 ` [PATCH 0/6] clockevent: " Viresh Kumar
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=55797A58.9020601@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).