linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V3 0/8] cpufreq: cleanups and reorganization
Date: Fri,  3 Jun 2016 10:58:44 +0530	[thread overview]
Message-ID: <cover.1464931080.git.viresh.kumar@linaro.org> (raw)

Hi Rafael,

This cleans up cpufreq core and few platform drivers a bit. Its mostly
around cleaning up the usage of cpufreq_frequency_table_target(), which
will be optimized in a separate series.

V2->V3:
- Fixed an issue with cpu_cooling.c (Javi)
- Included 2 new patches from the other cleanup series.
- Added Acked-by: from Javi for cpu_cooling.c

Viresh Kumar (8):
  ARM: davinci: Sort frequency table
  cpufreq: s3c24xx: Remove useless checks
  cpufreq: Remove cpufreq_frequency_get_table()
  cpufreq: ondemand: Don't keep a copy of freq_table pointer
  cpufreq: Drop freq-table param to cpufreq_frequency_table_target()
  cpufreq: Drop 'freq_table' argument of __target_index()
  cpufreq: Return index from cpufreq_frequency_table_target()
  cpufreq: davinci: Reuse cpufreq_generic_frequency_table_verify()

 Documentation/cpu-freq/cpu-drivers.txt |  8 ++---
 arch/arm/mach-davinci/da850.c          | 16 +++++----
 drivers/cpufreq/amd_freq_sensitivity.c | 10 +++---
 drivers/cpufreq/cpufreq.c              | 66 ++++++++++++----------------------
 drivers/cpufreq/cpufreq_ondemand.c     | 25 ++++++-------
 drivers/cpufreq/cpufreq_ondemand.h     |  1 -
 drivers/cpufreq/cpufreq_stats.c        |  3 +-
 drivers/cpufreq/davinci-cpufreq.c      | 22 +-----------
 drivers/cpufreq/freq_table.c           | 35 +++++++++---------
 drivers/cpufreq/powernv-cpufreq.c      |  5 ++-
 drivers/cpufreq/ppc_cbe_cpufreq_pmi.c  |  3 +-
 drivers/cpufreq/s3c24xx-cpufreq.c      | 33 ++++-------------
 drivers/cpufreq/s5pv210-cpufreq.c      |  8 ++---
 drivers/thermal/cpu_cooling.c          | 24 ++++++++++---
 include/linux/cpufreq.h                |  6 +---
 15 files changed, 100 insertions(+), 165 deletions(-)

-- 
2.7.1.410.g6faf27b


             reply	other threads:[~2016-06-03  5:29 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-03  5:28 Viresh Kumar [this message]
2016-06-03  5:28 ` [PATCH V3 1/8] ARM: davinci: Sort frequency table Viresh Kumar
2016-06-06  3:44   ` [PATCH V4 " Viresh Kumar
2016-06-07 10:27     ` Viresh Kumar
2016-06-03  5:28 ` [PATCH V3 2/8] cpufreq: s3c24xx: Remove useless checks Viresh Kumar
2016-06-03  5:28 ` [PATCH V3 3/8] cpufreq: Remove cpufreq_frequency_get_table() Viresh Kumar
2016-06-03  5:28 ` [PATCH V3 4/8] cpufreq: ondemand: Don't keep a copy of freq_table pointer Viresh Kumar
2016-06-03  5:28 ` [PATCH V3 5/8] cpufreq: Drop freq-table param to cpufreq_frequency_table_target() Viresh Kumar
2016-06-03  5:28 ` [PATCH V3 6/8] cpufreq: Drop 'freq_table' argument of __target_index() Viresh Kumar
2016-06-03  5:28 ` [PATCH V3 7/8] cpufreq: Return index from cpufreq_frequency_table_target() Viresh Kumar
2016-06-03  5:28 ` [PATCH V3 8/8] cpufreq: davinci: Reuse cpufreq_generic_frequency_table_verify() 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=cover.1464931080.git.viresh.kumar@linaro.org \
    --to=viresh.kumar@linaro.org \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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).