[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151017041055.GZ19018@linux>
Date: Sat, 17 Oct 2015 09:40:55 +0530
From: Viresh Kumar <viresh.kumar@...aro.org>
To: Stephen Boyd <sboyd@...eaurora.org>
Cc: Rob Herring <robh@...nel.org>, Rafael Wysocki <rjw@...ysocki.net>,
nm@...com, linaro-kernel@...ts.linaro.org,
linux-pm@...r.kernel.org, rob.herring@...aro.org,
lee.jones@...aro.org, Mark Brown <broonie@...nel.org>,
devicetree@...r.kernel.org,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
open list <linux-kernel@...r.kernel.org>,
Mark Rutland <mark.rutland@....com>,
Pawel Moll <pawel.moll@....com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>
Subject: Re: [PATCH 01/16] PM / OPP: Add 'supply-names' binding
On 16-10-15, 12:16, Stephen Boyd wrote:
> On 10/16, Viresh Kumar wrote:
> > On 15-10-15, 17:22, Stephen Boyd wrote:
> > > I'm lost why we need this property at all. What happened to using
> > >
> > > opp-microvolt-0 = <1 2 3>;
> > > opp-microvolt-1 = <1>;
> > > opp-microvolt-2 = <3 4 5>;
> > > etc.
> >
> > Perhaps you are confusing this with the bindings we came up for
> > picking right voltage levels based on the cuts/version of the hardware
> > we are running on. The problem that Lee Jones mentioned and that can
> > be used in your case as well.
>
> Isn't that what this patch series is for?
Hehe, no.
Okay here is the problem statement:
We have two supplies for a device and the device node will have
something like:
name1-supply = <&supply1>;
name2-supply = <&supply2>;
And the OPP node needs to have voltages for both of them:
opp-microvolt = <X1 Y1 Z1>, <X2 Y2 Z2>;
Where XYZ(1) are for supply1 and XYZ(2) are for supply2.
Now we need to identify the supplies for which the values are present
here and their order as well. How do we do that?
The way I am suggesting is to add a property in opp node which will
keep "name1" and "name2" in it.
--
viresh
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists