From: Fabio Baltieri <fabio.baltieri@linaro.org>
To: John Stultz <johnstul@us.ibm.com>, Arnd Bergmann <arnd@arndb.de>,
Thomas Gleixner <tglx@linutronix.de>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Cc: cpufreq@vger.kernel.org, linux-pm@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Fabio Baltieri <fabio.baltieri@linaro.org>
Subject: [PATCH 0/2] clocksource: nomadik-mtu: support timer-based delay
Date: Tue, 4 Dec 2012 11:10:43 +0100 [thread overview]
Message-ID: <1354615845-2758-1-git-send-email-fabio.baltieri@linaro.org> (raw)
Hi all,
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.
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(-)
--
1.7.12.1
next reply other threads:[~2012-12-04 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-04 10:10 Fabio Baltieri [this message]
2012-12-04 10:10 ` [PATCH 1/2] clocksource: nomadik-mtu: support timer-based delay 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 ` [PATCH 0/2] clocksource: nomadik-mtu: support timer-based delay Fabio Baltieri
2012-12-17 18:38 ` Linus Walleij
2012-12-17 18:59 ` John Stultz
2012-12-19 15:34 ` Linus Walleij
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=1354615845-2758-1-git-send-email-fabio.baltieri@linaro.org \
--to=fabio.baltieri@linaro.org \
--cc=arnd@arndb.de \
--cc=cpufreq@vger.kernel.org \
--cc=johnstul@us.ibm.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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).