linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: khilman@ti.com (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 00/10] cpufreq: OMAP: move into drivers, cleanups/fixes for v3.2
Date: Wed, 02 Nov 2011 15:02:37 -0700	[thread overview]
Message-ID: <4EB1BDFD.2060403@ti.com> (raw)
In-Reply-To: <1316725648-26710-1-git-send-email-khilman@ti.com>

Hi Dave,

On 09/22/2011 02:07 PM, Kevin Hilman wrote:
> This series moves the OMAP CPUfreq driver into drivers/cpufreq, add
> support for SMP devices (OMAP4+) and includes several cleanups and
> fixes from Nishanth Menon.
> 
> This series applies to v3.1-rc6, and is available here:
> 
>    git://github.com/khilman/linux-omap-pm.git for_3.2/omap-cpufreq
> 
> Kevin

Any chance of this making it in for v3.2?

Kevin

> Colin Cross (1):
>   cpufreq: OMAP: notify even with bad boot frequency
> 
> Nishanth Menon (6):
>   cpufreq: OMAP: move clk name decision to init
>   cpufreq: OMAP: deny initialization if no mpudev
>   cpufreq: OMAP: dont support !freq_table
>   cpufreq: OMAP: only supports OPP library
>   cpufreq: OMAP: put clk if cpu_init failed
>   cpufreq: OMAP: fix freq_table leak
> 
> Russell King (1):
>   cpufreq: OMAP: Add SMP support for OMAP4+
> 
> Santosh Shilimkar (1):
>   cpufreq: OMAP: cleanup for multi-SoC support, move into
>     drivers/cpufreq
> 
> Todd Poynor (1):
>   cpufreq: OMAP: Enable all CPUs in shared policy mask
> 
>  arch/arm/plat-omap/Makefile    |    1 -
>  arch/arm/plat-omap/cpu-omap.c  |  171 -------------------------
>  drivers/cpufreq/Makefile       |    1 +
>  drivers/cpufreq/omap-cpufreq.c |  271 ++++++++++++++++++++++++++++++++++++++++
>  4 files changed, 272 insertions(+), 172 deletions(-)
>  delete mode 100644 arch/arm/plat-omap/cpu-omap.c
>  create mode 100644 drivers/cpufreq/omap-cpufreq.c
> 

  parent reply	other threads:[~2011-11-02 22:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 21:07 [PATCH 00/10] cpufreq: OMAP: move into drivers, cleanups/fixes for v3.2 Kevin Hilman
2011-09-22 21:07 ` [PATCH 01/10] cpufreq: OMAP: cleanup for multi-SoC support, move into drivers/cpufreq Kevin Hilman
2011-09-22 21:53   ` Tony Lindgren
2011-09-23  9:21   ` [PATCH 01/10] cpufreq: OMAP: cleanup for multi-SoC support,move " Vishwanath Sripathy
2011-09-23 14:02     ` [PATCH 01/10] cpufreq: OMAP: cleanup for multi-SoC support, move " Kevin Hilman
2011-09-22 21:07 ` [PATCH 02/10] cpufreq: OMAP: Add SMP support for OMAP4+ Kevin Hilman
2011-09-22 23:11   ` Kevin Hilman
2013-08-29 10:02   ` Viresh Kumar
2013-08-29 13:37     ` Santosh Shilimkar
2013-08-29 13:39       ` Viresh Kumar
2013-08-29 13:42         ` Santosh Shilimkar
     [not found]           ` <CAKohpomco=TodaosVbvAhFSxrth9aZ1gh+VOHftG1w6nYWBsPg@mail.gmail.com>
2013-08-30  5:58             ` Viresh Kumar
2013-08-30 13:26             ` Santosh Shilimkar
2011-09-22 21:07 ` [PATCH 03/10] cpufreq: OMAP: Enable all CPUs in shared policy mask Kevin Hilman
2011-09-22 21:07 ` [PATCH 04/10] cpufreq: OMAP: notify even with bad boot frequency Kevin Hilman
2011-09-22 21:07 ` [PATCH 05/10] cpufreq: OMAP: move clk name decision to init Kevin Hilman
2011-09-22 21:07 ` [PATCH 06/10] cpufreq: OMAP: deny initialization if no mpudev Kevin Hilman
2011-09-22 21:07 ` [PATCH 07/10] cpufreq: OMAP: dont support !freq_table Kevin Hilman
2011-09-22 21:07 ` [PATCH 08/10] cpufreq: OMAP: only supports OPP library Kevin Hilman
2011-09-22 21:07 ` [PATCH 09/10] cpufreq: OMAP: put clk if cpu_init failed Kevin Hilman
2011-09-22 21:07 ` [PATCH 10/10] cpufreq: OMAP: fix freq_table leak Kevin Hilman
2011-11-02 22:02 ` Kevin Hilman [this message]
2011-11-02 22:08   ` [PATCH 00/10] cpufreq: OMAP: move into drivers, cleanups/fixes for v3.2 Dave Jones
2011-11-02 23:37     ` Kevin Hilman
2011-11-08 19:48     ` Kevin Hilman
2011-11-08 19:59       ` Dave Jones

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=4EB1BDFD.2060403@ti.com \
    --to=khilman@ti.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).