From mboxrd@z Thu Jan 1 00:00:00 1970 From: santosh.shilimkar@ti.com (Shilimkar, Santosh) Date: Tue, 3 Apr 2012 11:20:30 +0530 Subject: [PATCH 1/3] ARM: OMAP2+: 32k-counter: Use hwmod lookup to check presence of 32k timer In-Reply-To: <87sjgmt211.fsf@ti.com> References: <1326983304-14619-1-git-send-email-hvaibhav@ti.com> <4F672364.3020403@ti.com> <79CD15C6BA57404B839C016229A409A83182386C@DBDE01.ent.ti.com> <79CD15C6BA57404B839C016229A409A83183EA54@DBDE01.ent.ti.com> <79CD15C6BA57404B839C016229A409A83183EB47@DBDE01.ent.ti.com> <79CD15C6BA57404B839C016229A409A831840C2E@DBDE01.ent.ti.com> <79CD15C6BA57404B839C016229A409A831840E0C@DBDE01.ent.ti.com> <4F7570FC.8000907@ti.com> <79CD15C6BA57404B839C016229A409A831840F82@DBDE01.ent.ti.com> <87sjgmt211.fsf@ti.com> Message-ID: To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Tue, Apr 3, 2012 at 12:05 AM, Kevin Hilman wrote: > "Shilimkar, Santosh" writes: > > [...] > >> I don't personally like to add features which hardly anybody use and >> fundamentally broken with full kernel. > > Let's keep sane defaults, but not make it unreasonable to tweak eaither. > Exactly. Thanks for echoing the concern. > I suggest what has already been mentioned. > > Register both timers, but have the sync timer have a higher rating. ?On > AMxxx where there is no sync timer, GPtimer will be used. > Technically it's a hack just from clock precision point of view but I don't mind this. > For those who want to use GPtimer, they can boot using clocksource= to > override the default. > Sounds good to me. > Santosh is right, GPtimer will not work on a PM enabled kernel, but > there are lots of ways to use the cmdline to get a non-working kernel, > so that's OK by me. > > Let's just ensure that the boot-defaults are sane. > Absolutely. Regards Santosh