[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151022163052.GW8232@sirena.org.uk>
Date: Fri, 23 Oct 2015 01:30:52 +0900
From: Mark Brown <broonie@...nel.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>, nm@...com,
sboyd@...eaurora.org, linaro-kernel@...ts.linaro.org,
linux-pm@...r.kernel.org, rob.herring@...aro.org,
lee.jones@...aro.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>,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH 01/16] PM / OPP: Add 'supply-names' binding
On Fri, Sep 11, 2015 at 05:31:57PM +0530, Viresh Kumar wrote:
> +- supply-names: This is a required property, only if multiple supplies are
> + available for the device. Otherwise it is optional.
> +
> + This list is used to pass names of all the device supplies. The order of names
> + present here is important, as that should match the order in which values are
> + present in 'opp-microvolt' and 'opp-microamp' properties.
If we were going to add something like this (which I'm really not that
thrilled about due to their encouragement of bad practice as previously
discussed) it seems wrong to add it at the level of a specific binding
rather than as a general facility. I think I'm not entirely sold on
this use case though, I'll follow up to a later message in this
thread...
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists