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, Stephen Boyd <sboyd@codeaurora.org>,
Nishanth Menon <nm@ti.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH V3 00/10] PM / OPP: Fixes and cleanups
Date: Mon, 2 Jan 2017 14:40:54 +0530 [thread overview]
Message-ID: <cover.1483348138.git.viresh.kumar@linaro.org> (raw)
Hi,
Happy new year guys !!
This series fixes a memory leak (first patch) and does some cleanups to
the OPP core.
It is based of pm/linux-next branch.
This series is tested for few days by various build and boot bots:
- Kernel CI (Linaro)
- Fengguang Wu's bot (Intel)
V2->V3:
- Only the 7th patch is updated based on Stephen's comment.
- All the patches now have a Reviewed-by tag.
V1->V2:
- 6 out of 10 patches have received Acks from Stephen/MyungJoo.
- dev_pm_opp_get_suspend_opp_freq() return freq in Hz now
- s/opp_table/table in _opp_allocate()
- Improved comment over _opp_add() defining its return types
- opp_rcu_lockdep_assert() added at few places
- Dropped a useless comment
--
viresh
Viresh Kumar (10):
PM / OPP: Fix memory leak while adding duplicate OPPs
PM / OPP: Remove useless TODO
PM / OPP: Rename _allocate_opp() to _opp_allocate()
PM / OPP: Error out on failing to add static OPPs for v1 bindings
PM / OPP: Add light weight _opp_free() routine
PM / OPP: Rename and split _dev_pm_opp_remove_table()
PM / OPP: Don't allocate OPP table from _opp_allocate()
PM / OPP: Rename dev_pm_opp_get_suspend_opp() and return OPP rate
PM / OPP: Don't expose srcu_head to register notifiers
PM / OPP: Split out part of _add_opp_table() and _remove_opp_table()
drivers/base/power/opp/core.c | 293 ++++++++++++++++++++++++++----------------
drivers/base/power/opp/of.c | 89 +++++++------
drivers/base/power/opp/opp.h | 11 +-
drivers/cpufreq/cpufreq-dt.c | 7 +-
drivers/devfreq/devfreq.c | 26 +---
include/linux/pm_opp.h | 20 ++-
6 files changed, 253 insertions(+), 193 deletions(-)
--
2.7.1.410.g6faf27b
next reply other threads:[~2017-01-02 9:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 9:10 Viresh Kumar [this message]
2017-01-02 9:10 ` [PATCH V3 01/10] PM / OPP: Fix memory leak while adding duplicate OPPs Viresh Kumar
2017-01-02 9:10 ` [PATCH V3 02/10] PM / OPP: Remove useless TODO Viresh Kumar
2017-01-02 9:10 ` [PATCH V3 03/10] PM / OPP: Rename _allocate_opp() to _opp_allocate() Viresh Kumar
2017-01-02 9:10 ` [PATCH V3 04/10] PM / OPP: Error out on failing to add static OPPs for v1 bindings Viresh Kumar
2017-01-02 9:10 ` [PATCH V3 05/10] PM / OPP: Add light weight _opp_free() routine Viresh Kumar
2017-01-02 9:11 ` [PATCH V3 06/10] PM / OPP: Rename and split _dev_pm_opp_remove_table() Viresh Kumar
2017-01-02 9:11 ` [PATCH V3 07/10] PM / OPP: Don't allocate OPP table from _opp_allocate() Viresh Kumar
2017-01-02 9:11 ` [PATCH V3 08/10] PM / OPP: Rename dev_pm_opp_get_suspend_opp() and return OPP rate Viresh Kumar
2017-01-02 9:11 ` [PATCH V3 09/10] PM / OPP: Don't expose srcu_head to register notifiers Viresh Kumar
2017-01-02 9:11 ` [PATCH V3 10/10] PM / OPP: Split out part of _add_opp_table() and _remove_opp_table() 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.1483348138.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=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=sboyd@codeaurora.org \
--cc=vincent.guittot@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).