From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rajendra Nayak <rnayak@codeaurora.org>
Cc: Rob Herring <robh@kernel.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
Kevin Hilman <khilman@kernel.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Rafael Wysocki <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Sudeep Holla <sudeep.holla@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V8 3/3] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values
Date: Tue, 2 Jan 2018 12:03:27 +0530 [thread overview]
Message-ID: <20180102063327.GB15166@vireshk-i7> (raw)
In-Reply-To: <3721988e-fa13-c5dc-9ee6-490ed9b4b767@codeaurora.org>
On 02-01-18, 11:35, Rajendra Nayak wrote:
> I would want to reiterate what I have been saying for a while, that for these patches
> to be usable on any qualcomm platform completely we need support to associate
> multiple power-domains to a single device which is missing today.
Sure, but I had the understanding based on our last communication that
you are going to go with partial support for now and multiple domain
thing will be done later on.
> What I have been testing with these patches is to move a single user (MMC, which BTW does not
> have to put requests on multiple powerdomains) to use this solution on a db820c (msm8996) device.
Right.
> Getting this merged now can open up issues for other devices (which can't move to this solution)
> since MMC alone would put requests to pull a *common* rail up/down while others can't.
Even on that I thought that you will artificially vote for a high
requirement for those devices from some platform code initially, and
remove that code once all the device drivers (you need) are updated to
post their own requirements.
--
viresh
next prev parent reply other threads:[~2018-01-02 6:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 10:21 [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains Viresh Kumar
2017-12-18 10:21 ` [PATCH V8 1/3] " Viresh Kumar
2017-12-21 22:06 ` Rob Herring
2017-12-18 10:21 ` [PATCH V8 2/3] OPP: Introduce "required-opp" property Viresh Kumar
2017-12-20 8:23 ` Ulf Hansson
2017-12-20 8:26 ` Viresh Kumar
2017-12-21 22:26 ` Rob Herring
2017-12-22 5:28 ` Viresh Kumar
2017-12-18 10:21 ` [PATCH V8 3/3] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values Viresh Kumar
2017-12-26 20:29 ` Rob Herring
2017-12-27 8:56 ` Viresh Kumar
2017-12-27 21:54 ` Rob Herring
2017-12-28 4:37 ` Viresh Kumar
2017-12-29 0:32 ` Stephen Boyd
2017-12-29 4:58 ` Viresh Kumar
2018-01-05 22:19 ` Stephen Boyd
2018-01-08 4:16 ` Viresh Kumar
2018-01-10 2:54 ` Stephen Boyd
2018-01-10 5:37 ` Viresh Kumar
2018-01-13 0:46 ` Stephen Boyd
2018-01-02 6:05 ` Rajendra Nayak
2018-01-02 6:33 ` Viresh Kumar [this message]
2018-01-03 7:20 ` [PATCH V8 0/3] OPP: Allow OPP table to be used for power-domains Viresh Kumar
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=20180102063327.GB15166@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@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