From: Viresh Kumar <viresh.kumar@linaro.org>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Kevin Hilman <khilman@baylibre.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
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 13:58:08 +0530 [thread overview]
Message-ID: <20161027082808.GD10423@vireshk-i7> (raw)
In-Reply-To: <CAKfTPtDD=nGiOno9z2q3pcgQFB8RJwTb1fSmOZJRPZEy0Et8DA@mail.gmail.com>
On 27-10-16, 09:17, Vincent Guittot wrote:
> The M3 core takes only care of the voltage but not the clock ?
Yes. The is handled normally.
> Just to be sure to understand the problem:
> -There is no real voltage value but instead an opaque index that has
> to be used with frequency instead of a voltage.
> -This index is used by the M3 core to set voltages but M3 core doesn't
> set the clock which is managed by Linux.
> -The M3 core takes only one index input for the whole voltage domain
> and Linux must aggregate the constraints (with probably a max policy)
> of all devices that belong this domain
>
> Am i missing something ?
No. All matches to my understanding of the problem.
--
viresh
next prev parent reply other threads:[~2016-10-27 15:35 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
2016-10-27 7:17 ` Vincent Guittot
2016-10-27 8:28 ` Viresh Kumar [this message]
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=20161027082808.GD10423@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