From: Stephen Boyd <sboyd@codeaurora.org>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
John Stultz <john.stultz@linaro.org>,
Thomas Gleixner <tglx@linutronix.de>,
Mark Rutland <mark.rutland@arm.com>,
Marc Zyngier <Marc.Zyngier@arm.com>
Subject: [PATCHv3/RESEND 2/4] clocksource: arch_timer: Pass clock event to set_mode callback
Date: Fri, 21 Jun 2013 10:39:19 -0700 [thread overview]
Message-ID: <1371836361-20574-3-git-send-email-sboyd@codeaurora.org> (raw)
In-Reply-To: <1371836361-20574-1-git-send-email-sboyd@codeaurora.org>
There isn't any reason why we don't pass the event here and we'll
need it in the near future for memory mapped arch timers anyway.
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <Marc.Zyngier@arm.com>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
---
drivers/clocksource/arm_arch_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
index 053d846..220da0c 100644
--- a/drivers/clocksource/arm_arch_timer.c
+++ b/drivers/clocksource/arm_arch_timer.c
@@ -140,7 +140,7 @@ static int __cpuinit arch_timer_setup(struct clock_event_device *clk)
clk->cpumask = cpumask_of(smp_processor_id());
- clk->set_mode(CLOCK_EVT_MODE_SHUTDOWN, NULL);
+ clk->set_mode(CLOCK_EVT_MODE_SHUTDOWN, clk);
clockevents_config_and_register(clk, arch_timer_rate,
0xf, 0x7fffffff);
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv3/RESEND 2/4] clocksource: arch_timer: Pass clock event to set_mode callback
Date: Fri, 21 Jun 2013 10:39:19 -0700 [thread overview]
Message-ID: <1371836361-20574-3-git-send-email-sboyd@codeaurora.org> (raw)
In-Reply-To: <1371836361-20574-1-git-send-email-sboyd@codeaurora.org>
There isn't any reason why we don't pass the event here and we'll
need it in the near future for memory mapped arch timers anyway.
Cc: Mark Rutland <mark.rutland@arm.com>
Cc: Marc Zyngier <Marc.Zyngier@arm.com>
Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
---
drivers/clocksource/arm_arch_timer.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clocksource/arm_arch_timer.c b/drivers/clocksource/arm_arch_timer.c
index 053d846..220da0c 100644
--- a/drivers/clocksource/arm_arch_timer.c
+++ b/drivers/clocksource/arm_arch_timer.c
@@ -140,7 +140,7 @@ static int __cpuinit arch_timer_setup(struct clock_event_device *clk)
clk->cpumask = cpumask_of(smp_processor_id());
- clk->set_mode(CLOCK_EVT_MODE_SHUTDOWN, NULL);
+ clk->set_mode(CLOCK_EVT_MODE_SHUTDOWN, clk);
clockevents_config_and_register(clk, arch_timer_rate,
0xf, 0x7fffffff);
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-06-21 17:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-21 17:39 [PATCHv3/RESEND 0/4] Memory mapped architected timers Stephen Boyd
2013-06-21 17:39 ` Stephen Boyd
2013-06-21 17:39 ` [PATCHv3/RESEND 1/4] Documentation: Add memory mapped ARM architected timer binding Stephen Boyd
2013-06-21 17:39 ` Stephen Boyd
2013-06-21 17:39 ` Stephen Boyd [this message]
2013-06-21 17:39 ` [PATCHv3/RESEND 2/4] clocksource: arch_timer: Pass clock event to set_mode callback Stephen Boyd
2013-06-21 17:39 ` [PATCHv3/RESEND 3/4] clocksource: arch_timer: Push the read/write wrappers deeper Stephen Boyd
2013-06-21 17:39 ` Stephen Boyd
2013-06-21 17:39 ` [PATCHv3/RESEND 4/4] clocksource: arch_timer: Add support for memory mapped timers Stephen Boyd
2013-06-21 17:39 ` Stephen Boyd
2013-06-21 21:18 ` Thomas Gleixner
2013-06-21 21:18 ` Thomas Gleixner
2013-06-21 23:01 ` Stephen Boyd
2013-06-21 23:01 ` Stephen Boyd
2013-06-21 23:13 ` Thomas Gleixner
2013-06-21 23:13 ` Thomas Gleixner
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=1371836361-20574-3-git-send-email-sboyd@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=Marc.Zyngier@arm.com \
--cc=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--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.