[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <524E91D5.5020804@atmel.com>
Date: Fri, 4 Oct 2013 12:00:53 +0200
From: Nicolas Ferre <nicolas.ferre@...el.com>
To: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@...osoft.com>,
Thomas Gleixner <tglx@...utronix.de>,
LAK <linux-arm-kernel@...ts.infradead.org>
CC: Russell King - ARM Linux <linux@....linux.org.uk>,
<linux-kernel@...r.kernel.org>, Marc Pignat <marc.pignat@...s.ch>,
"Ludovic Desroches" <ludovic.desroches@...el.com>,
<john.stultz@...aro.org>, <kernel@...gutronix.de>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Ronald Wahl <ronald.wahl@...itan.com>
Subject: Re: Timekeeping on at91rm9200 [Was: [PATCH v2] clockevents: Sanitize
ticks to nsec conversion]
On 24/09/2013 23:11, Uwe Kleine-König :
> Hello Nicolas, hello Jean-Christophe,
>
> I expect you should be able to revert
>
> b7a8ca5 (ARM: at91: rm9200 fix time support)
>
> which reverted
>
> 838a2ae (ARM: use clockevents_config_and_register() where possible)
>
> for at91rm9200 on top of the patch this mail is a reply to.
>
> Can you please test that?
I have just tested that on at91rm9200-ek:
- revert the revert (!)
- experience the crash
- then apply the v2 patch
- and finally see it working nicely!
Thanks a lot for having corrected this. Now, do you want that I stack
this revert-of-revert on the AT91 git tree or you are able to apply it
through the clock git tree together with the patch that is fixing the
issue (it may prevent synchronization difficulties)? (BTW, I do not see
it yet in "next").
Anyway, if it is required, you can add my:
Tested-by: Nicolas Ferre <nicolas.ferre@...el.com>
Thanks, bye,
--
Nicolas Ferre
--
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