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,
Vincent Guittot <vincent.guittot@linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>, Nishanth Menon <nm@ti.com>,
Viresh Kumar <viresh.kumar@linaro.org>
Subject: [PATCH 0/4] PM / OPP: Minor cleanups
Date: Wed, 17 May 2017 10:10:31 +0530 [thread overview]
Message-ID: <cover.1494995911.git.viresh.kumar@linaro.org> (raw)
Hi,
Here are few cleanup patches for the OPP core. The first two simplify
the code that was written specifically due to the limitations that we
had because of RCUs. We don't RCUs anymore and this can be simplified.
The last two take care of specific corner cases.
Rebased over pm/linux-next and tested on Exynos dual core board.
Viresh Kumar (4):
PM / OPP: Reorganize _generic_set_opp_regulator()
PM / OPP: Don't create copy of regulators unnecessarily
PM / OPP: opp-microvolt is not optional if regulators are set
PM / OPP: Don't create debugfs "supply-0" directory unnecessarily
drivers/base/power/opp/core.c | 87 +++++++++++++++++-----------------------
drivers/base/power/opp/debugfs.c | 6 +--
drivers/base/power/opp/of.c | 11 ++++-
3 files changed, 49 insertions(+), 55 deletions(-)
--
2.13.0.303.g4ebf3021692d
next reply other threads:[~2017-05-17 4:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 4:40 Viresh Kumar [this message]
2017-05-17 4:40 ` [PATCH 1/4] PM / OPP: Reorganize _generic_set_opp_regulator() Viresh Kumar
2017-05-23 1:09 ` Stephen Boyd
2017-05-17 4:40 ` [PATCH 2/4] PM / OPP: Don't create copy of regulators unnecessarily Viresh Kumar
2017-05-23 1:10 ` Stephen Boyd
2017-05-17 4:40 ` [PATCH 3/4] PM / OPP: opp-microvolt is not optional if regulators are set Viresh Kumar
2017-05-23 1:20 ` Stephen Boyd
2017-05-17 4:40 ` [PATCH 4/4] PM / OPP: Don't create debugfs "supply-0" directory unnecessarily Viresh Kumar
2017-05-23 1:28 ` Stephen Boyd
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.1494995911.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).