Linux Power Management development
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	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 12:09:40 +0100	[thread overview]
Message-ID: <af9ab13a-6f77-5abe-e17f-c7dd6efa6d7e@arm.com> (raw)
In-Reply-To: <CAKohpokwTOZbbRP4XRV1jPoQ=gKxD2UKBYSXcZe8iBgDnr9-BQ@mail.gmail.com>



On 26/10/16 11:52, Viresh Kumar wrote:
> Hi Guys,
>
> I wanted to involve you guys to get a discussion going
> for a problem we want to solve, and so this mail.
>
>
> Platform details:
>
> Some of the Qualcom SoCs have the option to configure
> the performance level of their Power Domains. The performance
> levels are identified by integer values (lets say 0-9, 0 being the lowest).
>
> Another M3 core handles the *real* voltage scaling based on the input
> received (from software) in terms of these performance levels. The M3
> core translates the levels into a range of voltages (corners) and selects
> the right one by itself.
>

Just out of curiosity, what's the protocol used to communicate with this
M3. 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.

> Software needs to provide the performance level for the entire domain
> to the M3 core and so software also needs to handle performance requests
> from all the devices that lie in the domain X and find a Performance Level P,
> which can satisfy all the devices (normally the highest requrested level).
>

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 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. 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.

-- 
Regards,
Sudeep

[1] 
http://s3.amazonaws.com/connect.linaro.org/las16/Presentations/Tuesday/LAS16-200%20--%20%20SCMI%20-%20System%20Management%20and%20Control%20Interface.pdf

  reply	other threads:[~2016-10-26 11:09 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 [this message]
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
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=af9ab13a-6f77-5abe-e17f-c7dd6efa6d7e@arm.com \
    --to=sudeep.holla@arm.com \
    --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=viresh.kumar@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