All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linaro-kernel@lists.linaro.org, linux-kernel@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/3] clockevents/arm: Implement ->set_state_oneshot_stopped()
Date: Wed, 23 Dec 2015 16:59:11 +0530	[thread overview]
Message-ID: <cover.1450869375.git.viresh.kumar@linaro.org> (raw)

Hi Daniel/Thomas,

ONESHOT-STOPPED state was merged into mainline sometime back and doesn't
have any users until now.

This series implements the set_state_oneshot_stopped() callback for few
ARM clkevt drivers.

Which other clkevt drivers will you advice to update, if any?

Tested on ARM Exynos 5250 dual A15 board (1/3 and 3/3, 2/3 is compile
tested only but is changed as many ARM SoCs use it).
Rebased on v4.4-rc6.

Viresh Kumar (3):
  clockevents/arm_arch_timer: Implement ->set_state_oneshot_stopped()
  clockevents/arm_global_timer: Implement ->set_state_oneshot_stopped()
  clockevents/exynos_mct: Implement ->set_state_oneshot_stopped()

 drivers/clocksource/arm_arch_timer.c   | 4 ++++
 drivers/clocksource/arm_global_timer.c | 1 +
 drivers/clocksource/exynos_mct.c       | 2 ++
 3 files changed, 7 insertions(+)

-- 
2.7.0.rc1.186.g94414c4


             reply	other threads:[~2015-12-23 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-23 11:29 Viresh Kumar [this message]
2015-12-23 11:29 ` [PATCH 1/3] clockevents/arm_arch_timer: Implement ->set_state_oneshot_stopped() Viresh Kumar
2015-12-23 11:29 ` [PATCH 2/3] clockevents/arm_global_timer: " Viresh Kumar
2015-12-23 11:29   ` Viresh Kumar
2015-12-23 11:29 ` [PATCH 3/3] clockevents/exynos_mct: " Viresh Kumar
2015-12-23 11:29   ` Viresh Kumar
2015-12-23 11:29   ` Viresh Kumar
2016-02-17 14:47 ` [PATCH 0/3] clockevents/arm: " 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.1450869375.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=daniel.lezcano@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.