[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150731062013.GR3159@codeaurora.org>
Date: Thu, 30 Jul 2015 23:20:13 -0700
From: Stephen Boyd <sboyd@...eaurora.org>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: Rafael Wysocki <rjw@...ysocki.net>, linaro-kernel@...ts.linaro.org,
linux-pm@...r.kernel.org, rob.herring@...aro.org,
arnd.bergmann@...aro.org, nm@...com, broonie@...nel.org,
mturquette@...libre.com, Sudeep.Holla@....com,
viswanath.puttagunta@...aro.org, l.stach@...gutronix.de,
thomas.petazzoni@...e-electrons.com,
linux-arm-kernel@...ts.infradead.org, ta.omasab@...il.com,
kesavan.abhilash@...il.com, khilman@...aro.org,
santosh.shilimkar@...cle.com, b.zolnierkie@...sung.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Len Brown <len.brown@...el.com>,
open list <linux-kernel@...r.kernel.org>,
Pavel Machek <pavel@....cz>
Subject: Re: [PATCH V3 07/16] PM / OPP: Add support to parse
"operating-points-v2" bindings
On 07/31, Viresh Kumar wrote:
> On 30-07-15, 22:51, Stephen Boyd wrote:
> > > + opp->u_volt = microvolt[0];
> > > + opp->u_volt_min = microvolt[1];
> > > + opp->u_volt_max = microvolt[2];
> >
> > Should the default be 0 and ULONG_MAX for volt_min/volt_max when
> > there's on element?
>
> I am not still sure how the regulator API is going to look like for
> this target/min/max thing. So, lets defer it until that is resolved.
> For now they are initialized to 0.
>
> And, because the user has just passed in a target voltage, maybe all
> three must be == u_volt. :)
>
Ok. Sounds fair enough.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
--
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