From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Hilman Subject: Re: [PATCH 1/3] ARM: OMAP2+: 32k-counter: Use hwmod lookup to check presence of 32k timer Date: Mon, 02 Apr 2012 11:35:38 -0700 Message-ID: <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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from na3sys009aog133.obsmtp.com ([74.125.149.82]:38886 "EHLO psmtp.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754333Ab2DBSfp (ORCPT ); Mon, 2 Apr 2012 14:35:45 -0400 Received: by dakh32 with SMTP id h32so2546402dak.23 for ; Mon, 02 Apr 2012 11:35:41 -0700 (PDT) In-Reply-To: (Santosh Shilimkar's message of "Sun, 1 Apr 2012 11:23:44 +0530") Sender: linux-omap-owner@vger.kernel.org List-Id: linux-omap@vger.kernel.org To: "Shilimkar, Santosh" Cc: Ming Lei , Tony Lindgren , "Hiremath, Vaibhav" , "linux-omap@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "marc.zyngier@arm.com" , "johnstul@us.ibm.com" , "Balbi, Felipe" , "Cousson, Benoit" , Paul Walmsley , "DebBarma, Tarun Kanti" "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. 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. For those who want to use GPtimer, they can boot using clocksource= to override the default. 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. Kevin From mboxrd@z Thu Jan 1 00:00:00 1970 From: khilman@ti.com (Kevin Hilman) Date: Mon, 02 Apr 2012 11:35:38 -0700 Subject: [PATCH 1/3] ARM: OMAP2+: 32k-counter: Use hwmod lookup to check presence of 32k timer In-Reply-To: (Santosh Shilimkar's message of "Sun, 1 Apr 2012 11:23:44 +0530") 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> Message-ID: <87sjgmt211.fsf@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org "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. 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. For those who want to use GPtimer, they can boot using clocksource= to override the default. 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. Kevin