[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMo8Bf+kQi7-7FfteB-DpdauSYJn4Ztjuy6oTOnVXk9aVBzUbQ@mail.gmail.com>
Date: Mon, 18 Nov 2013 00:27:42 +0400
From: Max Filippov <jcmvbkbc@...il.com>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: Chris Zankel <chris@...kel.net>,
"linux-xtensa@...ux-xtensa.org" <linux-xtensa@...ux-xtensa.org>,
LKML <linux-kernel@...r.kernel.org>,
John Stultz <john.stultz@...aro.org>
Subject: Re: [PATCH] xtensa: Switch to sched_clock_register()
On Sat, Nov 16, 2013 at 3:31 AM, Stephen Boyd <sboyd@...eaurora.org> 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.
>
> Signed-off-by: Stephen Boyd <sboyd@...eaurora.org>
> ---
>
> Patch is based on Linus' tip. Not event compile tested.
>
> arch/xtensa/kernel/time.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
Build and run-tested, appears to work.
Acked-by: Max Filippov <jcmvbkbc@...il.com>
Should it go through xtensa tree, or through some other tree as a part
of a bigger conversion series?
> diff --git a/arch/xtensa/kernel/time.c b/arch/xtensa/kernel/time.c
> index 9af3dd8..415c3f6 100644
> --- a/arch/xtensa/kernel/time.c
> +++ b/arch/xtensa/kernel/time.c
> @@ -36,7 +36,7 @@ static cycle_t ccount_read(struct clocksource *cs)
> return (cycle_t)get_ccount();
> }
>
> -static u32 notrace ccount_sched_clock_read(void)
> +static u64 notrace ccount_sched_clock_read(void)
> {
> return get_ccount();
> }
> @@ -141,7 +141,7 @@ void __init time_init(void)
> setup_irq(ccount_timer.evt.irq, &timer_irqaction);
> ccount_timer.irq_enabled = 1;
>
> - setup_sched_clock(ccount_sched_clock_read, 32, ccount_freq);
> + sched_clock_register(ccount_sched_clock_read, 32, ccount_freq);
> }
>
> /*
> --
> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
> hosted by The Linux Foundation
>
--
Thanks.
-- Max
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists