devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 3/4] arm64: dts: qcom: msm8996: add GCC's optional clock sources
Date: Mon, 20 Jun 2022 13:24:18 +0200	[thread overview]
Message-ID: <22f4ba43-2505-3000-24b6-b01d58d87e7f@linaro.org> (raw)
In-Reply-To: <20220620071936.1558906-4-dmitry.baryshkov@linaro.org>

On 20/06/2022 09:19, Dmitry Baryshkov wrote:
> Add missing GCC clock sources. This includes PCIe and USB PIPE and UFS
> symbol clocks.
> 
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
>  arch/arm64/boot/dts/qcom/msm8996.dtsi | 18 ++++++++++++++++--
>  1 file changed, 16 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi b/arch/arm64/boot/dts/qcom/msm8996.dtsi
> index e97f193aefd3..6c7380f86383 100644
> --- a/arch/arm64/boot/dts/qcom/msm8996.dtsi
> +++ b/arch/arm64/boot/dts/qcom/msm8996.dtsi
> @@ -689,8 +689,22 @@ gcc: clock-controller@300000 {
>  
>  			clocks = <&rpmcc RPM_SMD_BB_CLK1>,
>  				 <&rpmcc RPM_SMD_LN_BB_CLK>,
> -				 <&sleep_clk>;
> -			clock-names = "cxo", "cxo2", "sleep_clk";
> +				 <&sleep_clk>,
> +				 <&pciephy_0>,
> +				 <&pciephy_1>,
> +				 <&pciephy_2>,
> +				 <&ssusb_phy_0>,
> +				 <0>, <0>, <0>;

Since the clocks are optional, there is no need to pass <0> to them. I
think it does not bring any benefits.

> +			clock-names = "cxo",
> +				      "cxo2",
> +				      "sleep_clk",
> +				      "pcie_0_pipe_clk_src",
> +				      "pcie_1_pipe_clk_src",
> +				      "pcie_2_pipe_clk_src",
> +				      "usb3_phy_pipe_clk_src",
> +				      "ufs_rx_symbol_0_clk_src",
> +				      "ufs_rx_symbol_1_clk_src",
> +				      "ufs_tx_symbol_0_clk_src";
>  		};
>  
>  		tsens0: thermal-sensor@4a9000 {


Best regards,
Krzysztof

  reply	other threads:[~2022-06-20 11:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-20  7:19 [PATCH 0/4] arm64: dts: qcom: msm8996: add missing clock sources Dmitry Baryshkov
2022-06-20  7:19 ` [PATCH 1/4] dt-bindings: clock: qcom,gcc-msm8996: add more GCC " Dmitry Baryshkov
2022-06-20 11:22   ` Krzysztof Kozlowski
2022-07-07  2:31   ` (subset) " Bjorn Andersson
2022-06-20  7:19 ` [PATCH 2/4] arm64: dts: qcom: msm8996: correct #clock-cells for QMP PHY nodes Dmitry Baryshkov
2022-06-20  7:19 ` [PATCH 3/4] arm64: dts: qcom: msm8996: add GCC's optional clock sources Dmitry Baryshkov
2022-06-20 11:24   ` Krzysztof Kozlowski [this message]
2022-06-20 11:27     ` Dmitry Baryshkov
2022-06-20 12:35       ` Krzysztof Kozlowski
2022-06-20  7:19 ` [PATCH 4/4] arm64: dts: qcom: msm8996: add xo clock source to rpmcc Dmitry Baryshkov
2022-07-07  2:31 ` (subset) [PATCH 0/4] arm64: dts: qcom: msm8996: add missing clock sources Bjorn Andersson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=22f4ba43-2505-3000-24b6-b01d58d87e7f@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).