From: fabio.baltieri@linaro.org (Fabio Baltieri)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] clocksource: nomadik-mtu: support timer-based delay
Date: Mon, 17 Dec 2012 12:36:11 +0100 [thread overview]
Message-ID: <20121217113611.GA31470@balto.lan> (raw)
In-Reply-To: <1354615845-2758-1-git-send-email-fabio.baltieri@linaro.org>
Hi all,
On Tue, Dec 04, 2012 at 11:10:43AM +0100, Fabio Baltieri wrote:
> this implements timer-based delay support for nomadik and ux500
> platforms, using the MTU as time source, and marks the u8500 cpufreq
> driver as CPUFREQ_CONST_LOOPS accordingly.
>
> The patches are based on Arnd's arm-soc/ux500/mtu-clk branch, as that
> contains latest MTU driver developments, including a driver move/rename,
> but I can rebase if necessary.
The patches applies cleanly on current mainline now, as all dependencies
has already been merged, can this be considered for for merging too?
Also, the nomadik-mtu driver has been moved into drivers/clocksource so
do anybody knows if this this should end up into arm-soc or in the
clocksource tree?
Thanks,
Fabio
> Fabio Baltieri (2):
> clocksource: nomadik-mtu: support timer-based delay
> cpufreq: db8500: set CPUFREQ_CONST_LOOPS
>
> drivers/clocksource/nomadik-mtu.c | 11 +++++++++++
> drivers/cpufreq/db8500-cpufreq.c | 2 +-
> 2 files changed, 12 insertions(+), 1 deletion(-)
--
Fabio Baltieri
next prev parent reply other threads:[~2012-12-17 11:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 10:10 [PATCH 0/2] clocksource: nomadik-mtu: support timer-based delay Fabio Baltieri
2012-12-04 10:10 ` [PATCH 1/2] " Fabio Baltieri
2012-12-04 10:10 ` [PATCH 2/2] cpufreq: db8500: set CPUFREQ_CONST_LOOPS Fabio Baltieri
2012-12-17 18:24 ` Stephen Boyd
2012-12-17 22:03 ` Fabio Baltieri
2012-12-17 11:36 ` Fabio Baltieri [this message]
2012-12-17 18:38 ` [PATCH 0/2] clocksource: nomadik-mtu: support timer-based delay Linus Walleij
2012-12-17 18:59 ` John Stultz
2012-12-19 15:34 ` Linus Walleij
2012-12-19 16:18 ` John Stultz
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=20121217113611.GA31470@balto.lan \
--to=fabio.baltieri@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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).