From mboxrd@z Thu Jan  1 00:00:00 1970
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
Date: Mon, 24 Jan 2011 17:10:07 +0000
Subject: [PATCH v2] arm: Configure reference clock for Versatile
	Express timers
In-Reply-To: <F01D8B85CFF58440B2A13965FBA90CA45911F432AE@GEORGE.Emea.Arm.com>
References: <1295373883-21513-1-git-send-email-pawel.moll@arm.com>
	<20110124144753.GB22949@n2100.arm.linux.org.uk>
	<F01D8B85CFF58440B2A13965FBA90CA45911F4328E@GEORGE.Emea.Arm.com>
	<20110124161453.GB24104@n2100.arm.linux.org.uk>
	<F01D8B85CFF58440B2A13965FBA90CA45911F432AE@GEORGE.Emea.Arm.com>
Message-ID: <20110124171007.GI24104@n2100.arm.linux.org.uk>
To: linux-arm-kernel@lists.infradead.org
List-Id: linux-arm-kernel.lists.infradead.org

On Mon, Jan 24, 2011 at 04:38:20PM +0000, Pawel Moll wrote:
> > > I've removed them, because the sp804 driver is initializing these
> > > registers in sp804_clocksource_init() and sp804_set_mode(), just
> > > a jiffy later.
> > What if we have some other more preferable clock events which
> > rules in set_mode not being called?  How do we ensure that these
> > timers won't create some spurious interrupts?
> 
> Good point. The sp804_clockevent_init() should do this. A patch is just going out...

Right, I'm chucking your original patch out of my tree.