[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200321051612.GA5063@builder>
Date: Fri, 20 Mar 2020 22:16:12 -0700
From: Bjorn Andersson <bjorn.andersson@...aro.org>
To: Stephen Boyd <sboyd@...nel.org>
Cc: Michael Turquette <mturquette@...libre.com>,
Rob Herring <robh+dt@...nel.org>,
Andy Gross <agross@...nel.org>, linux-arm-msm@...r.kernel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, Rob Clark <robdclark@...il.com>
Subject: Re: [PATCH 2/4] clk: qcom: mmcc-msm8996: Properly describe GPU_GX
gdsc
On Fri 20 Mar 16:31 PDT 2020, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2020-03-18 22:39:00)
> > diff --git a/Documentation/devicetree/bindings/clock/qcom,mmcc.yaml b/Documentation/devicetree/bindings/clock/qcom,mmcc.yaml
> > index 85518494ce43..65d9aa790581 100644
> > --- a/Documentation/devicetree/bindings/clock/qcom,mmcc.yaml
> > +++ b/Documentation/devicetree/bindings/clock/qcom,mmcc.yaml
> > @@ -67,6 +67,10 @@ properties:
> > description:
> > Protected clock specifier list as per common clock binding
> >
> > + vdd_gfx-supply:
>
> Why not vdd-gfx-supply? What's with the underscore?
>
The pad is named "VDD_GFX" in the datasheet and the schematics. I see
that we've started y/_/-/ in some of the newly added bindings, would you
prefer I follow this?
Regards,
Bjorn
> > + description:
> > + Regulator supply for the GPU_GX GDSC
> > +
> > required:
> > - compatible
> > - reg
Powered by blists - more mailing lists