From: Stephen Boyd <sboyd@codeaurora.org>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
Lists linaro-kernel <linaro-kernel@lists.linaro.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>,
Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [Discussion] Performance levels of power domains
Date: Thu, 27 Oct 2016 17:22:02 -0700 [thread overview]
Message-ID: <20161028002202.GM26139@codeaurora.org> (raw)
In-Reply-To: <c11971ea-59aa-690a-95a3-d645ebb0074a@arm.com>
On 10/26, Sudeep Holla wrote:
>
>
> On 26/10/16 12:16, Viresh Kumar wrote:
> >On 26-10-16, 12:09, Sudeep Holla wrote:
>
> [...]
>
> >>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 ?
>
> Basically I wanted to know more details so that such system are also
> considered(I agree it may not have any impact on the protocol at all,
> but still good to consider them) when designing this new SCMI protocol.
>
There are a couple different wire protocols used to communicate
with the RPM on these platforms. The first one is at
drivers/mfd/qcom_rpm.c, and the second one is at
drivers/soc/qcom/smd-rpm.c. Bjorn upstreamed these drivers based
on the codeaurora sources.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-10-28 0:29 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 [this message]
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=20161028002202.GM26139@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bjorn.andersson@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=sudeep.holla@arm.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.