Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753147AbcD0QZB (ORCPT ); Wed, 27 Apr 2016 12:25:01 -0400 Received: from muru.com ([72.249.23.125]:52440 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752287AbcD0QY7 (ORCPT ); Wed, 27 Apr 2016 12:24:59 -0400 Date: Wed, 27 Apr 2016 09:24:52 -0700 From: Tony Lindgren To: Grygorii Strashko Cc: Russell King - ARM Linux , Liviu Dudau , Daniel Lezcano , Arnd Bergmann , Olof Johansson , linux-arm-kernel@lists.infradead.org, Sekhar Nori , linux-omap@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org, kernel@stlinux.com, linux-arm-kernel@axis.com, Florian Fainelli , Wei Xu , Shawn Guo , Sascha Hauer , Srinivas Kandagatla , Maxime Coquelin , Masahiro Yamada , Sudeep Holla , Jun Nie , Michal Simek , Jesper Nilsson , Lars Persson , Mike Looijmans Subject: Re: [PATCH v1] ARM: clocksource: make ARM_GLOBAL_TIMER selectable Message-ID: <20160427162452.GY5995@atomide.com> References: <1461684532-16848-1-git-send-email-grygorii.strashko@ti.com> <20160426160245.GI28464@e106497-lin.cambridge.arm.com> <571FC2EC.9090605@ti.com> <20160427104110.GU5783@n2100.arm.linux.org.uk> <5720BF19.6040600@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5720BF19.6040600@ti.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1521 Lines: 31 * Grygorii Strashko [160427 06:32]: > Hi Russell, > > On 04/27/2016 01:41 PM, Russell King - ARM Linux wrote: > > On Tue, Apr 26, 2016 at 10:35:08PM +0300, Grygorii Strashko wrote: > >> On 04/26/2016 07:02 PM, Liviu Dudau wrote: > >>> Well, SoC-B has the GT *and* the DT node, so what is the problem with > >>> enabling it for SoC-B? If there are reasons not to use the Global Timer > >>> on SoC-B, surely a better option would be to mark it in DT with status = "disabled"; > >> > >> This was rejected [2]. DT describes HW and if it is functional the status = "disabled" > >> is not good choice. > >> ARM GT can't be used as clocksource/sched_clock/clockevent when CPUFreq or > >> CPUIdle are enabled :(, and this is Linux specific functionality and > >> not HW description. > > > > Sorry, but we don't want to have to disable drivers in the kernel just > > because one platform has a problem (consider the single zImage case > > where it may be required that the global timer is enabled for some > > platform to boot - it becomes mandatory in single zImage at that point.) > > Sorry, but this patch doesn't disable anything. It provides possibility > to do a custom build with disabled ARM GT driver without Kernel code modification - > in my case RT-kernel and non-RT Kernel should run on same HW and > RT kernel should use ARM GT as clocksource/sched_clock, but > non-RT Kernel shouldn't. How about a kernel cmdline option for both local timers to disable the selected timer(s)? Tony