From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rafael Wysocki <rjw@rjwysocki.net>
Cc: linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/8] cpufreq: cleanups and reorganization
Date: Wed, 1 Jun 2016 16:04:14 +0530 [thread overview]
Message-ID: <cover.1464776797.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 later series.
This is just preparatory cleanup for that.
Also note that the 4th patch was sent earlier as well in a different
form and this is V3 of that.
Viresh Kumar (8):
ARM: s3c24xx: Sort cpufreq tables
cpufreq: s3c24xx: Remove useless checks
cpufreq: powerenv: Fix memory leak
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()
Documentation/cpu-freq/cpu-drivers.txt | 8 ++--
arch/arm/mach-s3c24xx/pll-s3c2410.c | 3 +-
arch/arm/mach-s3c24xx/pll-s3c2440-12000000.c | 1 +
arch/arm/mach-s3c24xx/pll-s3c2440-16934400.c | 1 +
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/freq_table.c | 35 +++++++--------
drivers/cpufreq/powernv-cpufreq.c | 18 ++++----
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 | 22 +++++++---
include/linux/cpufreq.h | 6 +--
16 files changed, 100 insertions(+), 143 deletions(-)
--
2.7.1.410.g6faf27b
next reply other threads:[~2016-06-01 10:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 10:34 Viresh Kumar [this message]
2016-06-01 10:34 ` [PATCH 1/8] ARM: s3c24xx: Sort cpufreq tables Viresh Kumar
2016-06-01 10:34 ` Viresh Kumar
2016-06-02 6:34 ` Krzysztof Kozlowski
2016-06-02 6:34 ` Krzysztof Kozlowski
2016-06-01 10:34 ` [PATCH 2/8] cpufreq: s3c24xx: Remove useless checks Viresh Kumar
2016-06-02 6:49 ` Krzysztof Kozlowski
2016-06-02 6:52 ` Viresh Kumar
2016-06-01 10:34 ` [PATCH 3/8] cpufreq: powerenv: Fix memory leak Viresh Kumar
2016-06-02 11:08 ` Michael Ellerman
2016-06-02 11:22 ` Viresh Kumar
2016-06-02 11:37 ` Michael Ellerman
2016-06-02 11:43 ` Viresh Kumar
2016-06-02 12:08 ` Michael Ellerman
2016-06-01 10:34 ` [PATCH V3 4/8] cpufreq: Remove cpufreq_frequency_get_table() Viresh Kumar
2016-06-01 10:34 ` [PATCH 5/8] cpufreq: ondemand: Don't keep a copy of freq_table pointer Viresh Kumar
2016-06-01 10:34 ` [PATCH 6/8] cpufreq: Drop freq-table param to cpufreq_frequency_table_target() Viresh Kumar
2016-06-01 10:34 ` [PATCH 7/8] cpufreq: Drop 'freq_table' argument of __target_index() Viresh Kumar
2016-06-01 10:34 ` [PATCH 8/8] cpufreq: Return index from cpufreq_frequency_table_target() Viresh Kumar
2016-06-01 16:47 ` [PATCH 0/8] cpufreq: cleanups and reorganization 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=cover.1464776797.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=linaro-kernel@lists.linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.