linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	shawn.guo@linaro.org, sboyd@codeaurora.org,
	linux-arm-msm@vger.kernel.org, spk.linux@gmail.com,
	thomas.ab@samsung.com, t.figa@samsung.com,
	thomas.petazzoni@free-electrons.com,
	pramod.gurav@smartplayin.com
Subject: Re: [PATCH V3 00/10] CPUFreq: cpufreq-cpu0 updates for 3.{17|18 ?}
Date: Thu, 28 Aug 2014 10:16:31 -0400	[thread overview]
Message-ID: <53FF39BF.4040006@ti.com> (raw)
In-Reply-To: <cover.1409201048.git.viresh.kumar@linaro.org>

On Thursday 28 August 2014 01:52 AM, Viresh Kumar wrote:
> Hi Rafael,
> 
> I am sending this again, but without the controversial part this time. I have
> dropped last two patches which were about detecting clock sharing among CPUs.
> Would fix up that later once other Maintainers get in sync about the bindings.
> 
> So, what's left here ? These are mostly updates/reorders which can be applied
> the patches which I have dropped now. These are all well reviewed and tested
> by others. Getting them in shouldn't break anything, I believe. Its better
> people start using the updates we already have, otherwise they will keep on
> sending fixes they get (The way Pramod Gurav tried it today).
> 
> Can we please get them in 3.17 if its still allowed? Or -next otherwise.
> 
> V2: https://lkml.org/lkml/2014/7/1/358
> 
> Rebased over: 3.17-rc2
> 
> git://git.linaro.org/people/viresh.kumar/linux.git cpufreq/cpu0-updates-v3
> 
> V2->V3: Dropped few patches, nothing much.
> 
I just hope that binding related discussion don't die because the series
has been moved on. Ofcourse the rest of the patches can move forward.

Feel free to add my ack if you need one


> 
> Viresh Kumar (10):
>   cpufreq: Add support for per-policy driver data
>   cpufreq: cpu0: Update Module Author
>   cpufreq: cpu0: don't validate clock on clk_put()
>   cpufreq: cpu0: print relevant error when we defer probe
>   cpufreq: cpu0: use dev_{err|warn|dbg} instead of pr_{err|warn|debug}
>   cpufreq: cpu0: Move per-cluster initialization code to ->init()
>   cpufreq: cpu0: try regulators with name "cpu-supply"
>   cpufreq: cpu0: Make allocate_resources() work for any CPU
>   cpufreq: cpu0: rename driver and internals to 'cpufreq_generic'
>   cpufreq: generic: set platform_{driver|device} '.name' to
>     'cpufreq-generic'
> 
>  .../{cpufreq-cpu0.txt => cpufreq-generic.txt}      |   8 +-
>  arch/arm/mach-imx/imx27-dt.c                       |   2 +-
>  arch/arm/mach-imx/mach-imx51.c                     |   2 +-
>  arch/arm/mach-omap2/pm.c                           |   2 +-
>  arch/arm/mach-shmobile/board-ape6evm-reference.c   |   2 +-
>  arch/arm/mach-shmobile/cpufreq.c                   |   2 +-
>  arch/arm/mach-shmobile/setup-sh73a0.c              |   4 +-
>  arch/arm/mach-zynq/common.c                        |   2 +-
>  drivers/cpufreq/Kconfig                            |  10 +-
>  drivers/cpufreq/Kconfig.arm                        |   2 +-
>  drivers/cpufreq/Makefile                           |   2 +-
>  drivers/cpufreq/cpufreq-cpu0.c                     | 248 --------------
>  drivers/cpufreq/cpufreq-generic.c                  | 363 +++++++++++++++++++++
>  drivers/cpufreq/exynos4210-cpufreq.c               |   2 +-
>  drivers/cpufreq/exynos4x12-cpufreq.c               |   2 +-
>  drivers/cpufreq/exynos5250-cpufreq.c               |   2 +-
>  drivers/cpufreq/highbank-cpufreq.c                 |   6 +-
>  drivers/cpufreq/s5pv210-cpufreq.c                  |   2 +-
>  include/linux/cpufreq.h                            |   3 +
>  19 files changed, 392 insertions(+), 274 deletions(-)
>  rename Documentation/devicetree/bindings/cpufreq/{cpufreq-cpu0.txt => cpufreq-generic.txt} (85%)
>  delete mode 100644 drivers/cpufreq/cpufreq-cpu0.c
>  create mode 100644 drivers/cpufreq/cpufreq-generic.c
> 

  parent reply	other threads:[~2014-08-28 14:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28  5:52 [PATCH V3 00/10] CPUFreq: cpufreq-cpu0 updates for 3.{17|18 ?} Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 01/10] cpufreq: Add support for per-policy driver data Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 02/10] cpufreq: cpu0: Update Module Author Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 03/10] cpufreq: cpu0: don't validate clock on clk_put() Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 04/10] cpufreq: cpu0: print relevant error when we defer probe Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 05/10] cpufreq: cpu0: use dev_{err|warn|dbg} instead of pr_{err|warn|debug} Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 06/10] cpufreq: cpu0: Move per-cluster initialization code to ->init() Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 07/10] cpufreq: cpu0: try regulators with name "cpu-supply" Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 08/10] cpufreq: cpu0: Make allocate_resources() work for any CPU Viresh Kumar
2014-08-28  5:52 ` [PATCH V3 09/10] cpufreq: cpu0: rename driver and internals to 'cpufreq_generic' Viresh Kumar
2014-09-08 23:34   ` Rafael J. Wysocki
2014-09-08 23:18     ` Stephen Boyd
2014-09-08 23:39       ` Rafael J. Wysocki
2014-09-08 23:52         ` Rafael J. Wysocki
2014-09-09  0:01           ` Stephen Boyd
2014-09-09  4:47             ` Viresh Kumar
2014-09-09 13:29               ` Rafael J. Wysocki
2014-09-09 13:52                 ` Viresh Kumar
2014-09-09  0:02           ` Rafael J. Wysocki
2014-08-28  5:52 ` [PATCH V3 10/10] cpufreq: generic: set platform_{driver|device} '.name' to 'cpufreq-generic' Viresh Kumar
2014-08-28 14:16 ` Santosh Shilimkar [this message]
2014-09-01  6:40   ` [PATCH V3 00/10] CPUFreq: cpufreq-cpu0 updates for 3.{17|18 ?} Viresh Kumar

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=53FF39BF.4040006@ti.com \
    --to=santosh.shilimkar@ti.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pramod.gurav@smartplayin.com \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.org \
    --cc=shawn.guo@linaro.org \
    --cc=spk.linux@gmail.com \
    --cc=t.figa@samsung.com \
    --cc=thomas.ab@samsung.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --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;
as well as URLs for NNTP newsgroup(s).