From: pawel.moll@arm.com (Pawel Moll)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ARM: vexpress/TC2: cpufreq support
Date: Mon, 21 Oct 2013 11:46:04 +0100 [thread overview]
Message-ID: <1382352364.3332.4.camel@hornet> (raw)
In-Reply-To: <1382349534-31502-1-git-send-email-Sudeep.KarkadaNagesha@arm.com>
On Mon, 2013-10-21 at 10:58 +0100, Sudeep KarkadaNagesha wrote:
> Sudeep KarkadaNagesha (5):
> cpufreq: arm-big-little: use clk_get instead of clk_get_sys
> ARM: vexpress/TC2: add support for CPU DVFS
> ARM: vexpress/TC2: add cpu clock support
> cpufreq: arm_big_little: add vexpress SPC interface driver
> ARM: vexpress/TC2: register vexpress-spc cpufreq device
>
> arch/arm/mach-vexpress/Kconfig | 12 ++
> arch/arm/mach-vexpress/Makefile | 3 +-
> arch/arm/mach-vexpress/spc.c | 366 ++++++++++++++++++++++++++++++++-
> arch/arm/mach-vexpress/spc.h | 2 +-
> arch/arm/mach-vexpress/tc2_pm.c | 7 +-
For the vexpress bits and pieces:
Acked-by: Pawel Moll <pawel.moll@arm.com>
Thanks!
Pawe?
next prev parent reply other threads:[~2013-10-21 10:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-21 9:58 [PATCH v2 0/5] ARM: vexpress/TC2: cpufreq support Sudeep KarkadaNagesha
2013-10-21 9:58 ` [PATCH v2 1/5] cpufreq: arm-big-little: use clk_get instead of clk_get_sys Sudeep KarkadaNagesha
2013-10-21 9:58 ` [PATCH v2 2/5] ARM: vexpress/TC2: add support for CPU DVFS Sudeep KarkadaNagesha
2013-10-21 9:58 ` [PATCH v2 3/5] ARM: vexpress/TC2: add cpu clock support Sudeep KarkadaNagesha
2013-10-21 9:58 ` [PATCH v2 4/5] cpufreq: arm_big_little: add vexpress SPC interface driver Sudeep KarkadaNagesha
2013-10-21 9:58 ` [PATCH v2 5/5] ARM: vexpress/TC2: register vexpress-spc cpufreq device Sudeep KarkadaNagesha
2013-10-21 10:46 ` Pawel Moll [this message]
2013-10-22 8:22 ` [PATCH v2 0/5] ARM: vexpress/TC2: cpufreq support Viresh Kumar
2013-10-22 9:51 ` Sudeep KarkadaNagesha
2013-10-22 17:38 ` Sudeep KarkadaNagesha
2013-10-22 22:05 ` Rafael J. Wysocki
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=1382352364.3332.4.camel@hornet \
--to=pawel.moll@arm.com \
--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).