[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51FFDF63.1090505@samsung.com>
Date: Tue, 06 Aug 2013 02:22:43 +0900
From: Kukjin Kim <kgene.kim@...sung.com>
To: Stephen Boyd <sboyd@...eaurora.org>
CC: arm@...nel.org, Kukjin Kim <kgene.kim@...sung.com>,
Ben Dooks <ben-linux@...ff.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 17/18] ARM: SAMSUNG: Switch to sched_clock_register()
On 08/01/13 07:31, 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.
>
> Cc: Ben Dooks<ben-linux@...ff.org>
> Cc: Kukjin Kim<kgene.kim@...sung.com>
Acked-by: Kukjin Kim <kgene.kim@...sung.com>
Thanks,
Kukjin
> Signed-off-by: Stephen Boyd<sboyd@...eaurora.org>
> ---
> arch/arm/plat-samsung/samsung-time.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm/plat-samsung/samsung-time.c b/arch/arm/plat-samsung/samsung-time.c
> index 2957075..1e2119b 100644
> --- a/arch/arm/plat-samsung/samsung-time.c
> +++ b/arch/arm/plat-samsung/samsung-time.c
> @@ -312,7 +312,7 @@ static void __iomem *samsung_timer_reg(void)
> * this wraps around for now, since it is just a relative time
> * stamp. (Inspired by U300 implementation.)
> */
> -static u32 notrace samsung_read_sched_clock(void)
> +static u64 notrace samsung_read_sched_clock(void)
> {
> void __iomem *reg = samsung_timer_reg();
>
> @@ -337,7 +337,7 @@ static void __init samsung_clocksource_init(void)
> samsung_time_setup(timer_source.source_id, TCNT_MAX);
> samsung_time_start(timer_source.source_id, PERIODIC);
>
> - setup_sched_clock(samsung_read_sched_clock, TSIZE, clock_rate);
> + sched_clock_register(samsung_read_sched_clock, TSIZE, clock_rate);
>
> if (clocksource_mmio_init(samsung_timer_reg(), "samsung_clocksource_timer",
> clock_rate, 250, TSIZE, clocksource_mmio_readl_down))
--
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