linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Abel Vesa <abel.vesa@linaro.org>
To: Pavankumar Kondeti <quic_pkondeti@quicinc.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: qcom: sm8550: fix xo clock source in cpufreq-hw node
Date: Tue, 17 Jan 2023 13:35:32 +0200	[thread overview]
Message-ID: <Y8aIBEbU2l7wVmJb@linaro.org> (raw)
In-Reply-To: <20230117093533.3710000-1-quic_pkondeti@quicinc.com>

On 23-01-17 15:05:33, Pavankumar Kondeti wrote:
> Currently, available frequencies for all CPUs are appearing as 2x
> of the actual frequencies. Use xo clock source as bi_tcxo in the
> cpufreq-hw node to fix this.

Yep, it seems that way. Thanks for this!

> 
> Signed-off-by: Pavankumar Kondeti <quic_pkondeti@quicinc.com>

Tested-by: Abel Vesa <abel.vesa@linaro.org>

> ---
>  arch/arm64/boot/dts/qcom/sm8550.dtsi | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sm8550.dtsi b/arch/arm64/boot/dts/qcom/sm8550.dtsi
> index 59756ec11564..a551ded31ddf 100644
> --- a/arch/arm64/boot/dts/qcom/sm8550.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm8550.dtsi
> @@ -2522,7 +2522,7 @@ cpufreq_hw: cpufreq@17d91000 {
>  			      <0 0x17d92000 0 0x1000>,
>  			      <0 0x17d93000 0 0x1000>;
>  			reg-names = "freq-domain0", "freq-domain1", "freq-domain2";
> -			clocks = <&rpmhcc RPMH_CXO_CLK>, <&gcc GCC_GPLL0>;
> +			clocks = <&bi_tcxo_div2>, <&gcc GCC_GPLL0>;
>  			clock-names = "xo", "alternate";
>  			interrupts = <GIC_SPI 30 IRQ_TYPE_LEVEL_HIGH>,
>  				     <GIC_SPI 31 IRQ_TYPE_LEVEL_HIGH>,
> -- 
> 2.25.1
> 

  reply	other threads:[~2023-01-17 11:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-06 20:10 [PATCH v9 00/10] arm64: dts: Add base device tree files for SM8550 Abel Vesa
2023-01-06 20:10 ` [PATCH v9 01/10] dt-bindings: arm: qcom: Document SM8550 SoC and boards Abel Vesa
2023-01-06 20:10 ` [PATCH v9 02/10] arm64: dts: qcom: Add base SM8550 dtsi Abel Vesa
2023-01-17  9:14   ` Pavan Kondeti
2023-01-17  9:35     ` [PATCH] arm64: dts: qcom: sm8550: fix xo clock source in cpufreq-hw node Pavankumar Kondeti
2023-01-17 11:35       ` Abel Vesa [this message]
2023-01-17 11:42       ` Neil Armstrong
2023-01-18 23:55       ` (subset) " Bjorn Andersson
2023-01-06 20:10 ` [PATCH v9 03/10] arm64: dts: qcom: Add pm8010 pmic dtsi Abel Vesa
2023-01-06 20:10 ` [PATCH v9 04/10] arm64: dts: qcom: Add PM8550 " Abel Vesa
2023-01-06 20:10 ` [PATCH v9 05/10] arm64: dts: qcom: Add PM8550b " Abel Vesa
2023-01-06 20:10 ` [PATCH v9 06/10] arm64: dts: qcom: Add PM8550ve " Abel Vesa
2023-01-06 20:10 ` [PATCH v9 07/10] arm64: dts: qcom: Add PM8550vs " Abel Vesa
2023-01-06 20:10 ` [PATCH v9 08/10] arm64: dts: qcom: Add PMK8550 " Abel Vesa
2023-01-06 20:10 ` [PATCH v9 09/10] arm64: dts: qcom: Add PMR735d " Abel Vesa
2023-01-06 20:10 ` [PATCH v9 10/10] arm64: dts: qcom: Add base SM8550 MTP dts Abel Vesa
2023-01-10 18:40 ` (subset) [PATCH v9 00/10] arm64: dts: Add base device tree files for SM8550 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=Y8aIBEbU2l7wVmJb@linaro.org \
    --to=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_pkondeti@quicinc.com \
    /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).