From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Thu, 19 Jan 2012 05:09:26 -0800 Subject: [RFC PATCH 1/5] arm:omap1/2/3/4:Convert 32k-Sync clocksource driver to platform_driver In-Reply-To: <20120118145032.GO16726@n2100.arm.linux.org.uk> References: <1326886086-27313-1-git-send-email-hvaibhav@ti.com> <1326886086-27313-2-git-send-email-hvaibhav@ti.com> <20120118115952.GM16726@n2100.arm.linux.org.uk> <79CD15C6BA57404B839C016229A409A8317A9AA2@DBDE01.ent.ti.com> <20120118141147.GN16726@n2100.arm.linux.org.uk> <4F16D66F.2000602@arm.com> <79CD15C6BA57404B839C016229A409A8317A9C39@DBDE01.ent.ti.com> <4F16DB10.8060806@arm.com> <20120118145032.GO16726@n2100.arm.linux.org.uk> Message-ID: <20120119130926.GF22818@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Russell King - ARM Linux [120118 06:18]: > On Wed, Jan 18, 2012 at 02:45:36PM +0000, Marc Zyngier wrote: > > Can't you instead use the ARM sched_clock framework? > > OMAP does, and has done for quite some time. The problem is these > patches are against an old kernel. Additionally we're already handling the 32k timer or not case already on omap1 as it does not exist on 1510, so there should only minimal patching needed AFAIK. Tony