From: Stefan Agner <stefan@agner.ch>
To: Mason <mpeg.blue@free.fr>
Cc: Linux ARM <linux-arm-kernel@lists.infradead.org>,
cpufreq <cpufreq@vger.kernel.org>,
Linux PM <linux-pm@vger.kernel.org>,
DT <devicetree@vger.kernel.org>
Subject: Re: Delays, clocks, timers, hrtimers, etc
Date: Fri, 06 Feb 2015 22:31:41 +0100 [thread overview]
Message-ID: <266c7b1ff2d1a8ba0ae4866f4fb4eca5@agner.ch> (raw)
In-Reply-To: <54D52F84.9050600@free.fr>
On 2015-02-06 22:17, Mason wrote:
> 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)
The changes have been accepted and went upstream in the 3.19 merge
window, see
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=81c4831907fb00efdc97093b09e333009a57d005
> Do you also use the ARM local timers in your port?
> Is there generic code to handle them?
It seems that there has been support for local timers once, but has been
removed. But I'm not aware of the details:
https://lkml.org/lkml/2013/2/22/49
--
Stefan
prev parent reply other threads:[~2015-02-06 21:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 13:16 Delays, clocks, timers, hrtimers, etc Mason
2015-01-29 13:57 ` Mason
2015-02-03 12:09 ` Russell King - ARM Linux
2015-02-06 20:25 ` Stefan Agner
2015-02-06 21:17 ` Mason
2015-02-06 21:31 ` Stefan Agner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=266c7b1ff2d1a8ba0ae4866f4fb4eca5@agner.ch \
--to=stefan@agner.ch \
--cc=cpufreq@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=mpeg.blue@free.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).