From: Viresh Kumar <viresh.kumar@linaro.org>
To: Rob Herring <robh@kernel.org>, Mark Brown <broonie@kernel.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
nm@ti.com, sboyd@codeaurora.org, linaro-kernel@lists.linaro.org,
linux-pm@vger.kernel.org, lee.jones@linaro.org,
devicetree@vger.kernel.org,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
open list <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Pawel Moll <pawel.moll@arm.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: [PATCH 02/16] PM / OPP: Add 'opp-microvolt-triplets' binding
Date: Tue, 15 Sep 2015 09:00:27 +0530 [thread overview]
Message-ID: <20150915033027.GJ32551@linux> (raw)
In-Reply-To: <55F72E65.6000205@kernel.org>
[+Cc Mark, I thought I cc'd him earlier, but no, I cc'd him only for
the first patch]
On 14-09-15, 15:30, Rob Herring wrote:
> On 09/11/2015 07:01 AM, Viresh Kumar wrote:
> > If 'opp-microvolt' is used to specify values for multiple regulators,
> > then we need this additional information to know if the values passed
> > should be treated as <target> or <target min max>.
>
> Can't you determine this implicitly from # of cells / # of regulators
> being either 1 or 3?
I thought the #<name>-cells property is used to pass arguments along with the
phandle, so something like this:
supply0: regulator@f8000000 {
regulator-cells = 1;
...
}
cpu@1 {
cpu-supply = <&supply0 XYZ>
}
But if we can define something like:
supply0: regulator@f8000000 {
regulator-cells or microvolt-cells = 1 or 3;
...
}
And then do:
cpu@1 {
cpu-supply = <&supply0>
operating-points-v2 = "&opp-table";
}
opp-table: table {
...
opp0 {
opp-hz = ...;
...
opp-microvolt = <one or three values here>
}
}
then it will be very simple. Also, this would mean that with multiple
regulators, we can have one regulator supporting single microvolts
value and other supporting tar/min/max values..
> >
> > This is because, DT doesn't differentiate between these two styles:
> >
> > prop = <x>, <y>, <z>;
> > prop = <x y z>;
> >
> > Cc: devicetree@vger.kernel.org
> > Signed-off-by: Viresh Kumar <viresh.kumar@linaro.org>
> > ---
> > Documentation/devicetree/bindings/opp/opp.txt | 14 ++++++++++++++
> > 1 file changed, 14 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt
> > index 8759bc4783ed..719603b87353 100644
> > --- a/Documentation/devicetree/bindings/opp/opp.txt
> > +++ b/Documentation/devicetree/bindings/opp/opp.txt
> > @@ -76,6 +76,16 @@ This describes the OPPs belonging to a device. This node can have following
> > present here is important, as that should match the order in which values are
> > present in 'opp-microvolt' and 'opp-microamp' properties.
> >
> > +- opp-microvolt-triplets: This is a required property, only if multiple supplies
> > + are available for the device. Otherwise it is ignored.
> > +
> > + 'opp-microvolt' can be present in two forms: <target> or <target min max>, per
> > + power-supply. 'opp-microvolt-triplets' property is used to find the form in
> > + which 'opp-microvolt' is present.
> > +
> > + If present, then 'opp-microvolt' must be present in <target min max> form,
> > + else in <target> form.
>
> This implies that bindings currently with triplets are wrong since they
> will be missing opp-microvolt-triplets.
Yeah, the bindings are incomplete, but there are no users yet, which
need the triplet thing. So, its all working just fine.
--
viresh
next prev parent reply other threads:[~2015-09-15 3:30 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 12:01 [PATCH 00/16] PM / OPP: multiple regulators & opp-transition support Viresh Kumar
2015-09-11 12:01 ` [PATCH 01/16] PM / OPP: Add 'supply-names' binding Viresh Kumar
2015-09-14 20:22 ` Rob Herring
[not found] ` <55F72C97.2030306-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
2015-09-15 2:47 ` Viresh Kumar
2015-10-08 9:27 ` Viresh Kumar
2015-10-16 0:22 ` Stephen Boyd
2015-10-16 6:02 ` Viresh Kumar
2015-10-16 19:16 ` Stephen Boyd
2015-10-17 4:10 ` Viresh Kumar
2015-10-21 13:18 ` Viresh Kumar
2015-10-22 16:39 ` Mark Brown
2015-10-27 8:19 ` Viresh Kumar
2015-10-28 8:17 ` Mark Brown
[not found] ` <20151028081742.GC28319-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-10-29 23:38 ` Stephen Boyd
2016-03-01 6:45 ` Viresh Kumar
2016-03-01 15:09 ` Nishanth Menon
2016-03-02 2:50 ` Mark Brown
2016-03-02 10:28 ` Viresh Kumar
2016-03-02 11:24 ` Mark Brown
2016-03-02 15:26 ` Nishanth Menon
2016-03-02 15:30 ` Mark Brown
2016-03-02 15:43 ` Nishanth Menon
2015-10-22 16:30 ` Mark Brown
2015-09-11 12:01 ` [PATCH 02/16] PM / OPP: Add 'opp-microvolt-triplets' binding Viresh Kumar
2015-09-14 20:30 ` Rob Herring
2015-09-15 3:30 ` Viresh Kumar [this message]
2015-09-19 15:39 ` Mark Brown
2015-09-11 12:01 ` [PATCH 03/16] PM / OPP: Improve debug print messages with pr_fmt Viresh Kumar
2015-09-11 12:02 ` [PATCH 04/16] PM / OPP: Rename routines specific to old bindings with _v1 Viresh Kumar
2015-09-11 12:02 ` [PATCH 05/16] PM / OPP: Parse all power-supply related bindings together Viresh Kumar
2015-09-11 12:02 ` [PATCH 06/16] PM / OPP: Create separate structure for regulator/supplies Viresh Kumar
2015-09-11 12:02 ` [PATCH 07/16] PM / OPP: Add multiple regulators support Viresh Kumar
2015-09-11 12:02 ` [PATCH 08/16] PM / OPP: get/put regulators from OPP core Viresh Kumar
2015-09-11 12:02 ` [PATCH 09/16] PM / OPP: Disable OPPs that aren't supported by the regulators Viresh Kumar
2015-09-11 12:02 ` [PATCH 10/16] PM / OPP: Introduce dev_pm_opp_get_max_volt_latency() Viresh Kumar
2015-09-11 12:02 ` [PATCH 11/16] PM / OPP: Introduce dev_pm_opp_get_max_transition_latency() Viresh Kumar
2015-09-11 12:02 ` [PATCH 12/16] PM / OPP: Parse clock and voltage tolerance for v1 bindings Viresh Kumar
2015-09-11 12:02 ` [PATCH 13/16] PM / OPP: Manage device clk as well Viresh Kumar
2015-09-11 12:02 ` [PATCH 14/16] PM / OPP: Add dev_pm_opp_set_regulator() to specify regulator Viresh Kumar
2015-09-11 12:02 ` [PATCH 15/16] PM / OPP: Add dev_pm_opp_set_rate() Viresh Kumar
2015-09-11 12:02 ` [PATCH 16/16] PM / OPP: don't print error message for deferred probing 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=20150915033027.GJ32551@linux \
--to=viresh.kumar@linaro.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=pawel.moll@arm.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sboyd@codeaurora.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).