From: Stephen Boyd <sboyd@codeaurora.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
linaro-kernel@lists.linaro.org, linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
robh@kernel.org, d-gerlach@ti.com, broonie@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH V7 06/10] PM / OPP: Add infrastructure to manage multiple regulators
Date: Tue, 6 Dec 2016 16:39:15 -0800 [thread overview]
Message-ID: <20161207003915.GD4388@codeaurora.org> (raw)
In-Reply-To: <804d4f89c517f7a0b0bb98ef513c329fd5f76d39.1480564564.git.viresh.kumar@linaro.org>
On 12/01, Viresh Kumar wrote:
> This patch adds infrastructure to manage multiple regulators and updates
> the only user (cpufreq-dt) of dev_pm_opp_set{put}_regulator().
>
> This is preparatory work for adding full support for devices with
> multiple regulators.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> Tested-by: Dave Gerlach <d-gerlach@ti.com>
> ---
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-12-07 0:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-01 10:58 [PATCH V7 00/10] PM / OPP: Multiple regulator support Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 02/10] PM / OPP: Reword binding supporting multiple regulators per device Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 06/10] PM / OPP: Add infrastructure to manage multiple regulators Viresh Kumar
2016-12-07 0:39 ` Stephen Boyd [this message]
[not found] ` <cover.1480564564.git.viresh.kumar-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2016-12-01 10:58 ` [PATCH V7 01/10] PM / OPP: Fix incorrect cpu-supply property in binding Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 03/10] PM / OPP: Don't use OPP structure outside of rcu protected section Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 04/10] PM / OPP: Manage supply's voltage/current in a separate structure Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 05/10] PM / OPP: Pass struct dev_pm_opp_supply to _set_opp_voltage() Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 07/10] PM / OPP: Separate out _generic_set_opp() Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 10/10] PM / OPP: Don't assume platform doesn't have regulators Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 08/10] PM / OPP: Allow platform specific custom set_opp() callbacks Viresh Kumar
2016-12-01 10:58 ` [PATCH V7 09/10] PM / OPP: Don't WARN on multiple calls to dev_pm_opp_set_regulators() Viresh Kumar
2016-12-05 14:21 ` [PATCH V7 00/10] PM / OPP: Multiple regulator support Viresh Kumar
[not found] ` <CAKohpokXXhcrhzqs+iW+1kTYjyF47bHF0TupMxP=4cSqXOThtA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-06 1:34 ` Rafael J. Wysocki
[not found] ` <CAJZ5v0gykH+UwMvgU3SCVgxg9Ufe23zQ1o9bEvnjtafVqjLa8Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-06 3:15 ` Viresh Kumar
2016-12-07 0:37 ` Stephen Boyd
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=20161207003915.GD4388@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=broonie@kernel.org \
--cc=d-gerlach@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=viresh.kumar@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).