From: Viresh Kumar <viresh.kumar@linaro.org>
To: Stephen Boyd <sboyd@codeaurora.org>, robh+dt@kernel.org
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org, Nishanth Menon <nm@ti.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
rnayak@codeaurora.org, sudeep.holla@arm.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Viresh Kumar <vireshk@kernel.org>,
ulf.hansson@linaro.org, Kevin Hilman <khilman@kernel.org>
Subject: Re: [RFC V7 0/2] OPP: Allow OPP table to be used for power-domains
Date: Wed, 29 Nov 2017 09:44:35 +0530 [thread overview]
Message-ID: <20171129041435.GG11413@vireshk-i7> (raw)
In-Reply-To: <cover.1509453284.git.viresh.kumar@linaro.org>
On 31-10-17, 18:17, Viresh Kumar wrote:
> Hi,
>
> Now that the performance state of PM domains are supported by the kernel
> (merged in linux-next), I am trying once again to define the bindings
> which we dropped until the code is merged first.
@Rob/Stephen: Can I get Ack from you guys on this series, before I
apply them? Ulf has already reviewed these.
--
viresh
next prev parent reply other threads:[~2017-11-29 4:14 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 12:47 [RFC V7 0/2] OPP: Allow OPP table to be used for power-domains Viresh Kumar
2017-10-31 12:47 ` [RFC V7 1/2] " Viresh Kumar
2017-11-28 15:50 ` Ulf Hansson
[not found] ` <2b244ea0a09deaf50237fb8b7578273a8284499e.1509453284.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-11-29 16:46 ` Rob Herring
2017-11-30 4:48 ` Viresh Kumar
[not found] ` <cover.1509453284.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2017-10-31 12:47 ` [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values Viresh Kumar
2017-10-31 16:02 ` Rob Herring
2017-11-01 2:17 ` Viresh Kumar
[not found] ` <CAKohpokvQD4Z6YY6MRG8c+hnsS=Z52X4XhyTgC5FTgf7VuaNmw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-01 20:39 ` Rob Herring
[not found] ` <CAL_JsqK-qtAaM_Ou5NtxcWR3F_q=8rMPJUm-VqGtKhbtWe5SAQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-11-01 21:43 ` Stephen Boyd
2017-11-02 4:51 ` Viresh Kumar
2017-11-02 7:15 ` Stephen Boyd
2017-11-02 9:00 ` Viresh Kumar
2017-11-28 16:38 ` Ulf Hansson
2017-11-30 0:50 ` Stephen Boyd
[not found] ` <20171130005029.GC19419-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2017-11-30 6:59 ` Viresh Kumar
2017-12-14 7:30 ` Viresh Kumar
2017-12-26 20:23 ` Rob Herring
[not found] ` <CAL_Jsq+ntPMiSacpsx7M7VwSXsx+fRbHpX-KFNVpDj+bYdNCiQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-27 4:45 ` Viresh Kumar
2017-12-27 21:36 ` Rob Herring
[not found] ` <CAL_JsqJA-cCOLRwHC1ZegHEt9v7pMoxY6qXF7Taq3k19bU-k3w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-12-28 4:32 ` Viresh Kumar
2017-11-02 4:49 ` Viresh Kumar
2017-11-28 16:14 ` Ulf Hansson
2017-11-29 4:14 ` Viresh Kumar [this message]
2017-11-29 16:37 ` [RFC V7 0/2] OPP: Allow OPP table to be used for power-domains Rob Herring
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=20171129041435.GG11413@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=khilman@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=rnayak@codeaurora.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sudeep.holla@arm.com \
--cc=ulf.hansson@linaro.org \
--cc=vincent.guittot@linaro.org \
--cc=vireshk@kernel.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;
as well as URLs for NNTP newsgroup(s).