From: Daniel Lezcano <daniel.lezcano@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
John Stultz <john.stultz@linaro.org>,
linux-kernel@vger.kernel.org,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: Re: [PATCH 3/4] clocksource: sun4i: Switch to sched_clock_register()
Date: Tue, 19 Nov 2013 14:57:29 +0100 [thread overview]
Message-ID: <528B6E49.9020104@linaro.org> (raw)
In-Reply-To: <1384559315-18699-4-git-send-email-sboyd@codeaurora.org>
On 11/16/2013 12:48 AM, Stephen Boyd wrote:
> The 32 bit sched_clock interface now supports 64 bits. Upgrade to
> the 64 bit function to allow us to remove the 32 bit registration
> interface. While we're here, mark the sched_clock function as
> notrace to prevent ftrace recursion crashes.
>
> Cc: Maxime Ripard <maxime.ripard@free-electrons.com>
> Signed-off-by: Stephen Boyd <sboyd@codeaurora.org>
> ---
Hi Maxime,
could you have look to this patch ?
Thanks
-- Daniel
> drivers/clocksource/sun4i_timer.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/clocksource/sun4i_timer.c b/drivers/clocksource/sun4i_timer.c
> index 2fb4695..932d685 100644
> --- a/drivers/clocksource/sun4i_timer.c
> +++ b/drivers/clocksource/sun4i_timer.c
> @@ -138,7 +138,7 @@ static struct irqaction sun4i_timer_irq = {
> .dev_id = &sun4i_clockevent,
> };
>
> -static u32 sun4i_timer_sched_read(void)
> +static u64 notrace sun4i_timer_sched_read(void)
> {
> return ~readl(timer_base + TIMER_CNTVAL_REG(1));
> }
> @@ -170,7 +170,7 @@ static void __init sun4i_timer_init(struct device_node *node)
> TIMER_CTL_CLK_SRC(TIMER_CTL_CLK_SRC_OSC24M),
> timer_base + TIMER_CTL_REG(1));
>
> - setup_sched_clock(sun4i_timer_sched_read, 32, rate);
> + sched_clock_register(sun4i_timer_sched_read, 32, rate);
> clocksource_mmio_init(timer_base + TIMER_CNTVAL_REG(1), node->name,
> rate, 300, 32, clocksource_mmio_readl_down);
--
<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:[~2013-11-19 13:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 23:48 [PATCH 0/4] Convert setup_sched_clock() users in drivers/clocksource Stephen Boyd
2013-11-15 23:48 ` [PATCH 1/4] clocksource: arm_global_timer: Switch to sched_clock_register() Stephen Boyd
2013-11-18 9:51 ` srinivas kandagatla
2013-11-18 17:55 ` Stuart MENEFY
2013-11-15 23:48 ` [PATCH 2/4] clocksource: cadence_ttc_timer: " Stephen Boyd
2013-11-16 0:08 ` Sören Brinkmann
2013-11-15 23:48 ` [PATCH 3/4] clocksource: sun4i: " Stephen Boyd
2013-11-19 13:57 ` Daniel Lezcano [this message]
2013-11-19 15:56 ` Maxime Ripard
2013-11-15 23:48 ` [PATCH 4/4] clocksource: orion: " Stephen Boyd
2013-11-16 13:35 ` Sebastian Hesselbarth
2013-11-19 23:52 ` [PATCH 0/4] Convert setup_sched_clock() users in drivers/clocksource 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=528B6E49.9020104@linaro.org \
--to=daniel.lezcano@linaro.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.ripard@free-electrons.com \
--cc=sboyd@codeaurora.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 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).