linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Viresh Kumar <viresh.kumar@linaro.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Lee Jones <lee.jones@linaro.org>, Nishanth Menon <nm@ti.com>,
	Len Brown <len.brown@intel.com>,
	Linaro Kernel Mailman List <linaro-kernel@lists.linaro.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Stephen Boyd <sboyd@codeaurora.org>,
	open list <linux-kernel@vger.kernel.org>,
	Pavel Machek <pavel@ucw.cz>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Viresh Kumar <vireshk@kernel.org>
Subject: Re: [PATCH V3 2/2] PM / OPP: Parse 'opp-<prop>-<name>' bindings
Date: Fri, 11 Dec 2015 07:11:46 +0530	[thread overview]
Message-ID: <20151211014146.GE3612@ubuntu> (raw)
In-Reply-To: <4979368.7DaYzKUvM2@vostro.rjw.lan>

On 10-12-15, 22:45, Rafael J. Wysocki wrote:
> On Thursday, December 10, 2015 09:54:45 AM Lee Jones wrote:
> > On 9 December 2015 at 02:31, Viresh Kumar <viresh.kumar@linaro.org> wrote:
> > > OPP bindings (for few properties) allow a platform to choose a
> > > value/range among a set of available options. The options are present as
> > > opp-<prop>-<name>, where the platform needs to supply the <name> string.
> > >
> > > The OPP properties which allow such an option are: opp-microvolt and
> > > opp-microamp.
> > >
> > > Add support to the OPP-core to parse these bindings, by introducing
> > > dev_pm_opp_{set|put}_prop_name() APIs.
> > >
> > > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > > ---
> > >  drivers/base/power/opp/core.c | 165 ++++++++++++++++++++++++++++++++++++++----
> > >  drivers/base/power/opp/opp.h  |   2 +
> > >  include/linux/pm_opp.h        |   9 +++
> > >  3 files changed, 161 insertions(+), 15 deletions(-)
> > 
> > Tested-by: Lee Jones <lee.jones@linaro.org>
> 
> OK, so tentatively I can take these two.
> 
> What exectly does depend on them and how that thing is intended to be handled?

The other two patches from Lee, Perhaps he missed mentioning that in
his cover-letter.

[PICKME 0/2] cpufreq: New ST driver

They must be rebased on my patches as they use the new APIs defined
here.

-- 
viresh

  reply	other threads:[~2015-12-11  1:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09  2:31 [PATCH V3 0/2] PM / OPP: Parse opp-supported-hw/opp-<prop>-<name> bindings Viresh Kumar
2015-12-09  2:31 ` [PATCH V3 1/2] PM / OPP: Parse 'opp-supported-hw' binding Viresh Kumar
2015-12-10  9:55   ` Lee Jones
2015-12-09  2:31 ` [PATCH V3 2/2] PM / OPP: Parse 'opp-<prop>-<name>' bindings Viresh Kumar
2015-12-10  9:54   ` Lee Jones
2015-12-10 21:45     ` Rafael J. Wysocki
2015-12-11  1:41       ` Viresh Kumar [this message]
2016-01-05 10:31   ` Geert Uytterhoeven
2016-01-05 10:46     ` 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=20151211014146.GE3612@ubuntu \
    --to=viresh.kumar@linaro.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=lee.jones@linaro.org \
    --cc=len.brown@intel.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=pavel@ucw.cz \
    --cc=rjw@rjwysocki.net \
    --cc=sboyd@codeaurora.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).