From: Viresh Kumar <viresh.kumar@linaro.org>
To: ulf.hansson@linaro.org, Kevin Hilman <khilman@kernel.org>,
Len Brown <len.brown@intel.com>, Nishanth Menon <nm@ti.com>,
Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Stephen Boyd <sboyd@kernel.org>,
Viresh Kumar <vireshk@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
niklas.cassel@linaro.org, rnayak@codeaurora.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] PM / Domains: Allow performance state propagation
Date: Mon, 5 Nov 2018 12:06:42 +0530 [thread overview]
Message-ID: <cover.1541399301.git.viresh.kumar@linaro.org> (raw)
Hi,
This series adds performance state propagation support in genpd core.
The propagation happens from the sub-domains to their masters. More
details can be found in the individual commit logs.
This is tested on hikey960 by faking power domains in such a way that
the CPU devices have two power domains and both of them have the same
master domain. The CPU device, as well as its power domains have
"required-opps" property set and the performance requirement from the
CPU eventually configures all the domains (2 sub-domains and 1 master).
@Rajendra: Will it be possible for you to run some tests and tell me if
some stuff is still missing as per Qcom requirements ?
Based on opp/linux-next branch (which is 4.20-rc1 +
multiple-power-domain-support-in-opp-core).
--
viresh
Viresh Kumar (4):
OPP: Add dev_pm_opp_xlate_performance_state() helper
PM / Domains: Save OPP table pointer in genpd
PM / Domains: Factorize dev_pm_genpd_set_performance_state()
PM / Domains: Propagate performance state updates
drivers/base/power/domain.c | 204 +++++++++++++++++++++++++++---------
drivers/opp/core.c | 49 +++++++++
include/linux/pm_domain.h | 6 ++
include/linux/pm_opp.h | 7 ++
4 files changed, 217 insertions(+), 49 deletions(-)
--
2.19.1.568.g152ad8e3369a
next reply other threads:[~2018-11-05 6:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-05 6:36 Viresh Kumar [this message]
2018-11-05 6:36 ` [PATCH 1/4] OPP: Add dev_pm_opp_xlate_performance_state() helper Viresh Kumar
2018-11-21 5:04 ` Rajendra Nayak
2018-11-21 5:17 ` Viresh Kumar
2018-11-21 6:06 ` Viresh Kumar
2018-11-21 6:18 ` Rajendra Nayak
2018-11-22 6:08 ` Viresh Kumar
2018-11-23 9:11 ` Viresh Kumar
2018-11-23 9:55 ` Viresh Kumar
2018-11-05 6:36 ` [PATCH 2/4] PM / Domains: Save OPP table pointer in genpd Viresh Kumar
2018-11-05 6:36 ` [PATCH 3/4] PM / Domains: Factorize dev_pm_genpd_set_performance_state() Viresh Kumar
2018-11-05 6:36 ` [PATCH 4/4] PM / Domains: Propagate performance state updates Viresh Kumar
2018-11-21 5:03 ` Rajendra Nayak
2018-11-21 5:16 ` Viresh Kumar
2018-11-21 5:31 ` Rajendra Nayak
2018-11-21 5:41 ` Viresh Kumar
2018-11-21 5:42 ` Rajendra Nayak
2018-11-21 6:36 ` Viresh Kumar
2018-11-21 6:51 ` Rajendra Nayak
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.1541399301.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=khilman@kernel.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
--cc=nm@ti.com \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=sboyd@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=vireshk@kernel.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).