From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Boyd Subject: Re: [PATCH] arm64: dts: sdm845: Add videocc node Date: Mon, 26 Nov 2018 22:57:48 -0800 Message-ID: <154330186815.88331.12720647562079303842@swboyd.mtv.corp.google.com> References: <1541414117-27864-1-git-send-email-tdas@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Andy Gross , Doug Anderson , Taniya Das Cc: Michael Turquette , David Brown , Rajendra Nayak , linux-arm-msm , "open list:ARM/QUALCOMM SUPPORT" , linux-clk , LKML , devicetree@vger.kernel.org, Rob Herring List-Id: linux-arm-msm@vger.kernel.org Quoting Doug Anderson (2018-11-26 16:35:50) > Hi, > = > On Mon, Nov 5, 2018 at 2:35 AM Taniya Das wrote: > > > > This adds the video clock controller node to sdm845 based on the exampl= es > > in the bindings. > > > > Signed-off-by: Taniya Das > > --- > > arch/arm64/boot/dts/qcom/sdm845.dtsi | 8 ++++++++ > > 1 file changed, 8 insertions(+) > > > > diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi b/arch/arm64/boot/dts= /qcom/sdm845.dtsi > > index b72bdb0..91a281b 100644 > > --- a/arch/arm64/boot/dts/qcom/sdm845.dtsi > > +++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi > > @@ -8,6 +8,7 @@ > > #include > > #include > > #include > > +#include > > #include > > #include > > #include > > @@ -1256,6 +1257,13 @@ > > #power-domain-cells =3D <1>; > > }; > > > > + videocc: clock-controller@ab00000 { > > + compatible =3D "qcom,sdm845-videocc"; > > + reg =3D <0xab00000 0x10000>; > > + #clock-cells =3D <1>; > > + #power-domain-cells =3D <1>; > = > Any reason not to include "#reset-cells =3D <1>;" here? The bindings > list it as optional but I see no reason why we should leave it off. > The file "include/dt-bindings/clock/qcom,videocc-sdm845.h" seems to > include some #defines for resets. Even though the driver doesn't seem > like it supports it yet, it still should be fine to list it here. We should update the binding to make it a required property. It doesn't make any sense why that property would be optional given that the hardware either has support for resets or it doesn't.