[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5d66bf6d.1c69fb81.c7b73.8fdb@mx.google.com>
Date: Wed, 28 Aug 2019 10:52:44 -0700
From: Stephen Boyd <swboyd@...omium.org>
To: Niklas Cassel <niklas.cassel@...aro.org>
Cc: Andy Gross <agross@...nel.org>, Ilia Lin <ilia.lin@...nel.org>,
Nishanth Menon <nm@...com>, Viresh Kumar <vireshk@...nel.org>,
linux-arm-msm@...r.kernel.org, jorge.ramirez-ortiz@...aro.org,
bjorn.andersson@...aro.org, ulf.hansson@...aro.org,
Rob Herring <robh@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 06/14] dt-bindings: cpufreq: qcom-nvmem: Support pstates provided by a power domain
Quoting Niklas Cassel (2019-08-22 03:27:23)
> On Mon, Aug 19, 2019 at 10:59:36AM -0700, Stephen Boyd wrote:
> > Quoting Niklas Cassel (2019-08-19 03:09:57)
> > > +
> > > +soc {
> > > +....
> > > + cprpd: cpr@...8000 {
> >
> > Maybe node name should be 'avs' for the industry standard adaptive
> > voltage scaling acronym?
>
> I see where this is coming from, but "git grep avs" gives a single result.
>
> Also, since the label is cprpd, it doesn't make sense to simply rename the
> node name, and I don't think that avspd would be a good name, since it is
> less correct.
>
> So if you don't insist, I would prefer to leave it as it is.
>
How about 'power-controller'?
Powered by blists - more mailing lists