From: Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"cpufreq@vger.kernel.org" <cpufreq@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>
Subject: Re: [GIT PULL]: CPUFreq: ARM Updates for 3.13
Date: Tue, 29 Oct 2013 10:57:40 +0000 [thread overview]
Message-ID: <526F94A4.7080706@arm.com> (raw)
In-Reply-To: <CAKohpombdzugLe0Q2NUttrapJuSqMDz41ECdxcHfh5dtPgiV0Q@mail.gmail.com>
Hi Viresh,
On 28/10/13 21:49, Viresh Kumar wrote:
> Hi Rafael,
>
> I have pushed ARM cpufreq patches for v3.13, you can pull them from my
> repo. Sorry if I am late...
>
> The following changes since commit 959f58544b7f20c92d5eb43d1232c96c15c01bfb:
>
> Linux 3.12-rc7 (2013-10-27 16:12:03 -0700)
>
> are available in the git repository at:
>
> git://git.linaro.org/people/vireshk/linux.git cpufreq-next-for-3.13
>
> for you to fetch changes up to 2332c7a7a8c1979de68429dcdcb125037ef35f4b:
>
> cpufreq: arm_big_little: reconfigure switcher behavior at run time
> (2013-10-29 03:18:41 +0530)
>
> ----------------------------------------------------------------
> Nicolas Pitre (1):
> cpufreq: arm_big_little: reconfigure switcher behavior at run time
>
> Sudeep KarkadaNagesha (5):
> cpufreq: arm-big-little: use clk_get instead of clk_get_sys
This is already pulled by Rafael, I can see it in linux-pm.git. So you can drop
that.
> 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
>
I also see that the changes for renaming opp_* to dev_pm_opp_* are pulled in.
This requires some fixup in patch 2 and 4 in this list. I can fixup by rebasing
on Rafael's tree. Let me know if you need me to do that.
Regards,
Sudeep
> Viresh Kumar (1):
> cpufreq: arm_big_little: add in-kernel switching (IKS) support
>
> 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 +-
> drivers/cpufreq/Kconfig.arm | 8 +
> drivers/cpufreq/Makefile | 1 +
> drivers/cpufreq/arm_big_little.c | 420 ++++++++++++++++++++++++++++++---
> drivers/cpufreq/arm_big_little.h | 5 -
> drivers/cpufreq/vexpress-spc-cpufreq.c | 69 ++++++
> 10 files changed, 853 insertions(+), 40 deletions(-)
> create mode 100644 drivers/cpufreq/vexpress-spc-cpufreq.c
>
next prev parent reply other threads:[~2013-10-29 10:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 21:49 [GIT PULL]: CPUFreq: ARM Updates for 3.13 Viresh Kumar
2013-10-29 10:57 ` Sudeep KarkadaNagesha [this message]
2013-10-29 12:05 ` Rafael J. Wysocki
2013-10-29 12:00 ` Sudeep KarkadaNagesha
2013-10-29 12:13 ` 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=526F94A4.7080706@arm.com \
--to=sudeep.karkadanagesha@arm.com \
--cc=cpufreq@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nicolas.pitre@linaro.org \
--cc=rjw@rjwysocki.net \
--cc=viresh.kumar@linaro.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