clockevents_config_and_register is more clever and correct than doing it
by hand; so use it.
Signed-off-by: Uwe Kleine-König <[email protected]>
---
arch/arc/kernel/time.c | 7 ++-----
1 file changed, 2 insertions(+), 5 deletions(-)
diff --git a/arch/arc/kernel/time.c b/arch/arc/kernel/time.c
index 0e51e69..273df8e 100644
--- a/arch/arc/kernel/time.c
+++ b/arch/arc/kernel/time.c
@@ -227,12 +227,9 @@ void __attribute__((weak)) arc_local_timer_setup(unsigned int cpu)
{
struct clock_event_device *clk = &per_cpu(arc_clockevent_device, cpu);
- clockevents_calc_mult_shift(clk, arc_get_core_freq(), 5);
-
- clk->max_delta_ns = clockevent_delta2ns(ARC_TIMER_MAX, clk);
clk->cpumask = cpumask_of(cpu);
-
- clockevents_register_device(clk);
+ clockevents_config_and_register(clk, arc_get_core_freq(),
+ 0, ARC_TIMER_MAX)
/*
* setup the per-cpu timer IRQ handler - for all cpus
--
1.8.4.rc3
On 09/25/2013 02:35 AM, Uwe Kleine-K?nig wrote:
> clockevents_config_and_register is more clever and correct than doing it
> by hand; so use it.
>
> Signed-off-by: Uwe Kleine-K?nig <[email protected]>
Acked-by: Vineet Gupta <[email protected]>
Thx for the fix.
-Vineet
On Thu, Sep 26, 2013 at 12:01:49PM +0000, Vineet Gupta wrote:
> On 09/25/2013 02:35 AM, Uwe Kleine-K?nig wrote:
> > clockevents_config_and_register is more clever and correct than doing it
> > by hand; so use it.
> >
> > Signed-off-by: Uwe Kleine-K?nig <[email protected]>
>
> Acked-by: Vineet Gupta <[email protected]>
Thanks for the ack, but I expected that it will be you who takes that
patch. Am I wrong? Who will take it instead?
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
On 09/27/2013 01:47 PM, Uwe Kleine-K?nig wrote:
> On Thu, Sep 26, 2013 at 12:01:49PM +0000, Vineet Gupta wrote:
>> On 09/25/2013 02:35 AM, Uwe Kleine-K?nig wrote:
>>> clockevents_config_and_register is more clever and correct than doing it
>>> by hand; so use it.
>>>
>>> Signed-off-by: Uwe Kleine-K?nig <[email protected]>
>> Acked-by: Vineet Gupta <[email protected]>
> Thanks for the ack, but I expected that it will be you who takes that
> patch. Am I wrong? Who will take it instead?
Well that really depends - if there's a series of such fixes, people generally
route it thru mm or some such.
But, sure I can take it.
Thx again,
-Vineet
Hello,
On Fri, Sep 27, 2013 at 08:26:58AM +0000, Vineet Gupta wrote:
> On 09/27/2013 01:47 PM, Uwe Kleine-K?nig wrote:
> > On Thu, Sep 26, 2013 at 12:01:49PM +0000, Vineet Gupta wrote:
> >> On 09/25/2013 02:35 AM, Uwe Kleine-K?nig wrote:
> >>> clockevents_config_and_register is more clever and correct than doing it
> >>> by hand; so use it.
> >>>
> >>> Signed-off-by: Uwe Kleine-K?nig <[email protected]>
> >> Acked-by: Vineet Gupta <[email protected]>
> > Thanks for the ack, but I expected that it will be you who takes that
> > patch. Am I wrong? Who will take it instead?
>
> Well that really depends - if there's a series of such fixes, people generally
> route it thru mm or some such.
I still have a few such fixes in the queue, but as they are all
independant of each other I think it would be best if you took it.
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
On 09/27/2013 02:22 PM, Uwe Kleine-K?nig wrote:
> I still have a few such fixes in the queue, but as they are all
> independant of each other I think it would be best if you took it.
Queued up for 3.12-rc3