From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758945Ab2CSNE5 (ORCPT ); Mon, 19 Mar 2012 09:04:57 -0400 Received: from caramon.arm.linux.org.uk ([78.32.30.218]:51515 "EHLO caramon.arm.linux.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758908Ab2CSNEz (ORCPT ); Mon, 19 Mar 2012 09:04:55 -0400 Date: Mon, 19 Mar 2012 13:04:45 +0000 From: Russell King - ARM Linux To: Ajeet Yadav Cc: John Stultz , linux-kernel@vger.kernel.org, Steven Rostedt Subject: Re: Not able to use HIGH_RES_TIMERS on ARM Message-ID: <20120319130445.GN15988@n2100.arm.linux.org.uk> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.19 (2009-01-05) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Mar 19, 2012 at 06:31:44PM +0530, Ajeet Yadav wrote: > Hi John, refering to you patch: > > ARM: remove 'select GENERIC_TIME' > GENERIC_TIME is now enabled by default, so 'select GENERIC_TIME' is > redundant. Remove them. > > The following config's are not selectable: > config NO_HZ, config HIGH_RES_TIMERS, config IRQSOFF_TRACER, config > PREEMPT_TRACER > > As far as I know, ARM now uses GENERIC_TIME via the arch_getoffset() > infrastructure, i.e ARCH_USES_GETTIMEOFFSET=y No. It is possible to select these options, but only if your platform uses the clockevent and clocksource infrastructure. If you're using that, then you must _not_ select ARCH_USES_GETTIMEOFFSET. ARCH_USES_GETTIMEOFFSET is for compatibility with old unconverted platforms, which are _not_ possible to use the above features.