From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mason Subject: Re: Delays, clocks, timers, hrtimers, etc Date: Fri, 06 Feb 2015 13:17:56 -0800 Message-ID: <54D52F84.9050600@free.fr> References: <54C8E125.3070905@free.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: cpufreq-owner@vger.kernel.org To: Stefan Agner Cc: Linux ARM , cpufreq , Linux PM , DT List-Id: linux-pm@vger.kernel.org Stefan Agner wrote: > Just recently I added support of ARM global timer as clocksource for > Vybrid SoC. This SoC doesn't use cpufreq, hence it is safe to use the > ARM global timer. The nice thing of device tree is, the patch to add > support for that did not change a single line of code: > > http://thread.gmane.org/gmane.linux.kernel/1794460 Hello Stefan, Your changes are not yet accepted in mainline, are they? (I don't see them in 3.18.5) Do you also use the ARM local timers in your port? Is there generic code to handle them? Regards.