From: Viresh Kumar <viresh.kumar@linaro.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Lists linaro-kernel <linaro-kernel@lists.linaro.org>,
Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Mark Brown <broonie@kernel.org>,
"Nayak, Rajendra" <rnayak@codeaurora.org>,
Georgi Djakov <georgi.djakov@linaro.org>
Subject: Re: [Discussion] Performance levels of power domains
Date: Wed, 26 Oct 2016 16:46:42 +0530 [thread overview]
Message-ID: <20161026111642.GM9162@vireshk-i7> (raw)
In-Reply-To: <af9ab13a-6f77-5abe-e17f-c7dd6efa6d7e@arm.com>
On 26-10-16, 12:09, Sudeep Holla wrote:
> Just out of curiosity, what's the protocol used to communicate with this
> M3.
I will let Qcom guys answer this :)
> This is what we already have on Vexpress TC2 and Juno. Currently M3
> provides the information of voltage and frequency for each OPP, but that
> may change as it's not always constant.
Yeah, I do remember that. But it was always in terms of voltages and
so this thing is different here.
> That's interesting and this is where it's different and gets complex
> than what we have today. Do you have more details on this ?
I have written everything that I knew about it :)
> I am mainly interested as there are efforts to standardize these
> communication with M3 and there's WIP protocol development[1]. It would
> be good to see if this user-case is also considered.
What do you mean by that ?
> And yes I am
> interested in the problem you have explained below but just can't my
> head around it as I can't fully visualize such systems.
:)
--
viresh
next prev parent reply other threads:[~2016-10-26 11:16 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 [this message]
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
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=20161026111642.GM9162@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=broonie@kernel.org \
--cc=georgi.djakov@linaro.org \
--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=sudeep.holla@arm.com \
/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