* Grygorii Strashko <grygorii.strashko@xxxxxx> [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 -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
