From: Viresh Kumar <viresh.kumar@linaro.org>
To: Kevin Hilman <khilman@baylibre.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Vincent Guittot <vincent.guittot@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
"Nayak, Rajendra" <rnayak@codeaurora.org>,
Georgi Djakov <georgi.djakov@linaro.org>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [Discussion] Performance levels of power domains
Date: Thu, 27 Oct 2016 09:16:38 +0530 [thread overview]
Message-ID: <20161027034638.GA10423@vireshk-i7> (raw)
In-Reply-To: <7hvawfq6kh.fsf@baylibre.com>
On 26-10-16, 12:00, Kevin Hilman wrote:
> Yes. As I've suggested to qcom/linaro folks (off-list discussions), I
No one told me this story :)
> think extending genpd to handle performance states is a logical
> extension. Otherwise, you will be (re)inventing something that looks an
> awful lot like genpd anyways.
I completely agree. Runtime PM and genpd look to be the perfect
placeholder for such stuff. I actually tried to convince Ulf yesterday
on this and he wasn't sure if it will ever get accepted upstream and
that's when I started this thread :)
> The other related framework is per-device PM QoS which could be used to
> set constraints on specific devices, and the genpd governors would then
> be responsible for looking at the constraints and changing states as
> needed.
I am not sure if genpd governors are also background governors like
cpufreq, but we need to make sure that the voltage is raised after the
function requesting a change returns, so that the clk rate can be
increased then.
--
viresh
next prev parent reply other threads:[~2016-10-27 3:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 10:52 [Discussion] Performance levels of power domains Viresh Kumar
2016-10-26 11:09 ` Sudeep Holla
2016-10-26 11:16 ` Viresh Kumar
2016-10-26 11:21 ` Sudeep Holla
2016-10-28 0:22 ` Stephen Boyd
2016-10-28 8:52 ` Sudeep Holla
2016-10-26 19:00 ` Kevin Hilman
2016-10-27 3:46 ` Viresh Kumar [this message]
2016-10-27 7:17 ` Vincent Guittot
2016-10-27 8:28 ` Viresh Kumar
2016-10-27 10:14 ` Rafael J. Wysocki
2016-10-27 7:13 ` Vincent Guittot
2016-10-27 10:11 ` Rafael J. Wysocki
2016-10-27 10:23 ` Viresh Kumar
2016-10-27 10:26 ` Rafael J. Wysocki
2016-10-27 11:46 ` Ulf Hansson
2016-10-28 4:02 ` Viresh Kumar
2016-10-27 13:12 ` Sudeep K N
2016-10-27 17:24 ` Kevin Hilman
2016-11-09 11:46 ` Viresh Kumar
2016-11-10 19:14 ` Kevin Hilman
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=20161027034638.GA10423@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=broonie@kernel.org \
--cc=georgi.djakov@linaro.org \
--cc=khilman@baylibre.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=sboyd@codeaurora.org \
--cc=ulf.hansson@linaro.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