From: shawnguo@kernel.org (shawnguo at kernel.org)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 5/9] ARM: imx: set up set_next_event hook in imx_timer_data_init()
Date: Fri, 15 May 2015 16:11:43 +0800 [thread overview]
Message-ID: <1431677507-27420-6-git-send-email-shawnguo@kernel.org> (raw)
In-Reply-To: <1431677507-27420-1-git-send-email-shawnguo@kernel.org>
From: Shawn Guo <shawn.guo@linaro.org>
Function imx_timer_data_init() was there for setting up device specific
data, so let's move the setup of set_next_event hook into there.
Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
---
arch/arm/mach-imx/time.c | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-imx/time.c b/arch/arm/mach-imx/time.c
index c86e25922eb4..d79a00e24084 100644
--- a/arch/arm/mach-imx/time.c
+++ b/arch/arm/mach-imx/time.c
@@ -290,15 +290,11 @@ static struct clock_event_device clockevent_mxc = {
.name = "mxc_timer1",
.features = CLOCK_EVT_FEAT_ONESHOT,
.set_mode = mxc_set_mode,
- .set_next_event = mx1_2_set_next_event,
.rating = 200,
};
static int __init mxc_clockevent_init(void)
{
- if (timer_is_v2())
- clockevent_mxc.set_next_event = v2_set_next_event;
-
clockevent_mxc.cpumask = cpumask_of(0);
clockevents_config_and_register(&clockevent_mxc,
clk_get_rate(imxtm.clk_per),
@@ -351,15 +347,19 @@ static void __init imx_timer_data_init(void)
switch (imxtm.type) {
case GPT_TYPE_IMX1:
imxtm.gpt_setup_tctl = imx1_gpt_setup_tctl;
+ clockevent_mxc.set_next_event = mx1_2_set_next_event;
break;
case GPT_TYPE_IMX21:
imxtm.gpt_setup_tctl = imx21_gpt_setup_tctl;
+ clockevent_mxc.set_next_event = mx1_2_set_next_event;
break;
case GPT_TYPE_IMX31:
imxtm.gpt_setup_tctl = imx31_gpt_setup_tctl;
+ clockevent_mxc.set_next_event = v2_set_next_event;
break;
case GPT_TYPE_IMX6DL:
imxtm.gpt_setup_tctl = imx6dl_gpt_setup_tctl;
+ clockevent_mxc.set_next_event = v2_set_next_event;
break;
default:
BUG();
--
1.9.1
next prev parent reply other threads:[~2015-05-15 8:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 8:11 [PATCH 0/9] ARM: imx: move timer driver into drivers/clocksource shawnguo at kernel.org
2015-05-15 8:11 ` [PATCH 1/9] ARM: imx: move timer resources into a structure shawnguo at kernel.org
2015-05-15 16:36 ` Shenwei Wang
2015-05-19 7:57 ` Shawn Guo
2015-05-18 10:43 ` Daniel Lezcano
2015-05-19 7:58 ` Shawn Guo
2015-05-15 8:11 ` [PATCH 2/9] ARM: imx: define an enum for gpt timer device type shawnguo at kernel.org
2015-05-15 16:30 ` Shenwei Wang
2015-05-15 8:11 ` [PATCH 3/9] ARM: imx: initialize gpt device type for DT boot shawnguo at kernel.org
2015-05-15 8:11 ` [PATCH 4/9] ARM: imx: setup tctl register in device specific function shawnguo at kernel.org
2015-05-15 8:35 ` Arnd Bergmann
2015-05-19 8:08 ` Shawn Guo
2015-05-15 8:11 ` shawnguo at kernel.org [this message]
2015-05-15 8:11 ` [PATCH 6/9] ARM: imx: define gpt register offset per device type shawnguo at kernel.org
2015-05-15 8:34 ` Arnd Bergmann
2015-05-19 8:09 ` Shawn Guo
2015-05-15 8:11 ` [PATCH 7/9] ARM: imx: provide gpt device specific irq functions shawnguo at kernel.org
2015-05-15 8:11 ` [PATCH 8/9] ARM: imx: remove platform headers from timer driver shawnguo at kernel.org
2015-05-15 8:11 ` [PATCH 9/9] ARM: imx: move timer driver into drivers/clocksource shawnguo at kernel.org
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=1431677507-27420-6-git-send-email-shawnguo@kernel.org \
--to=shawnguo@kernel.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).