[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdY5_kDf2C=85cuNYya6_eeRbZ4Uu5FKQ2a76N=r8gtAtw@mail.gmail.com>
Date: Thu, 1 Dec 2011 14:03:58 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Yong Zhang <yong.zhang0@...il.com>
Cc: linux-kernel@...r.kernel.org, John Stultz <johnstul@...ibm.com>,
Thomas Gleixner <tglx@...utronix.de>,
Mattias Wallin <mattias.wallin@...ricsson.com>,
Jonas ABERG <jonas.aberg@...ricsson.com>
Subject: Re: [PATCH 2/3] clocksource: dbx500: convert to clocksource_register_hz()
On Thu, Dec 1, 2011 at 8:20 AM, Yong Zhang <yong.zhang0@...il.com> wrote:
> Convert clocksource_dbx500_prcmu to use clocksource_register_hz.
>
> Signed-off-by: Yong Zhang <yong.zhang0@...il.com>
> Cc: John Stultz <johnstul@...ibm.com>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Mattias Wallin <mattias.wallin@...ricsson.com>
> ---
> drivers/clocksource/clksrc-dbx500-prcmu.c | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/clocksource/clksrc-dbx500-prcmu.c b/drivers/clocksource/clksrc-dbx500-prcmu.c
> index 59feefe..74e8901 100644
> --- a/drivers/clocksource/clksrc-dbx500-prcmu.c
> +++ b/drivers/clocksource/clksrc-dbx500-prcmu.c
> @@ -52,7 +52,6 @@ static struct clocksource clocksource_dbx500_prcmu = {
> .name = "dbx500-prcmu-timer",
> .rating = 300,
> .read = clksrc_dbx500_prcmu_read,
> - .shift = 10,
> .mask = CLOCKSOURCE_MASK(32),
> .flags = CLOCK_SOURCE_IS_CONTINUOUS,
> };
> @@ -100,7 +99,5 @@ void __init clksrc_dbx500_prcmu_init(void __iomem *base)
> init_sched_clock(&cd, clksrc_dbx500_prcmu_update_sched_clock,
> 32, RATE_32K);
> #endif
> - clocksource_calc_mult_shift(&clocksource_dbx500_prcmu,
> - RATE_32K, SCHED_CLOCK_MIN_WRAP);
> - clocksource_register(&clocksource_dbx500_prcmu);
> + clocksource_register_hz(&clocksource_dbx500_prcmu, RATE_32K);
> }
> --
> 1.7.5.4
Looks good,
Acked-by: Linus Walleij <linus.walleij@...aro.org>
Thanks,
Linus Walleij
--
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