devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
	andersson@kernel.org
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, viresh.kumar@linaro.org
Subject: Re: [RESEND PATCH 11/12] arm64: dts: qcom: sm6375: Supply clock from cpufreq node to CPUs
Date: Thu, 16 Feb 2023 11:40:00 +0100	[thread overview]
Message-ID: <83e71d32-417b-a343-4a3e-aa7cf0fa6857@linaro.org> (raw)
In-Reply-To: <20230215070400.5901-12-manivannan.sadhasivam@linaro.org>



On 15.02.2023 08:03, Manivannan Sadhasivam wrote:
> Qualcomm platforms making use of CPUFreq HW Engine (EPSS/OSM) supply clocks
> to the CPU cores. But this relationship is not represented in DTS so far.
> 
> So let's make cpufreq node as the clock provider and CPU nodes as the
> consumers. The clock index for each CPU node is based on the frequency
> domain index.
> 
> Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>

Konrad
>  arch/arm64/boot/dts/qcom/sm6375.dtsi | 9 +++++++++
>  1 file changed, 9 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/qcom/sm6375.dtsi b/arch/arm64/boot/dts/qcom/sm6375.dtsi
> index 31b88c738510..58d3b4785401 100644
> --- a/arch/arm64/boot/dts/qcom/sm6375.dtsi
> +++ b/arch/arm64/boot/dts/qcom/sm6375.dtsi
> @@ -39,6 +39,7 @@ CPU0: cpu@0 {
>  			device_type = "cpu";
>  			compatible = "qcom,kryo660";
>  			reg = <0x0 0x0>;
> +			clocks = <&cpufreq_hw 0>;
>  			enable-method = "psci";
>  			next-level-cache = <&L2_0>;
>  			qcom,freq-domain = <&cpufreq_hw 0>;
> @@ -58,6 +59,7 @@ CPU1: cpu@100 {
>  			device_type = "cpu";
>  			compatible = "qcom,kryo660";
>  			reg = <0x0 0x100>;
> +			clocks = <&cpufreq_hw 0>;
>  			enable-method = "psci";
>  			next-level-cache = <&L2_100>;
>  			qcom,freq-domain = <&cpufreq_hw 0>;
> @@ -74,6 +76,7 @@ CPU2: cpu@200 {
>  			device_type = "cpu";
>  			compatible = "qcom,kryo660";
>  			reg = <0x0 0x200>;
> +			clocks = <&cpufreq_hw 0>;
>  			enable-method = "psci";
>  			next-level-cache = <&L2_200>;
>  			qcom,freq-domain = <&cpufreq_hw 0>;
> @@ -90,6 +93,7 @@ CPU3: cpu@300 {
>  			device_type = "cpu";
>  			compatible = "qcom,kryo660";
>  			reg = <0x0 0x300>;
> +			clocks = <&cpufreq_hw 0>;
>  			enable-method = "psci";
>  			next-level-cache = <&L2_300>;
>  			qcom,freq-domain = <&cpufreq_hw 0>;
> @@ -106,6 +110,7 @@ CPU4: cpu@400 {
>  			device_type = "cpu";
>  			compatible = "qcom,kryo660";
>  			reg = <0x0 0x400>;
> +			clocks = <&cpufreq_hw 0>;
>  			enable-method = "psci";
>  			next-level-cache = <&L2_400>;
>  			qcom,freq-domain = <&cpufreq_hw 0>;
> @@ -122,6 +127,7 @@ CPU5: cpu@500 {
>  			device_type = "cpu";
>  			compatible = "qcom,kryo660";
>  			reg = <0x0 0x500>;
> +			clocks = <&cpufreq_hw 0>;
>  			enable-method = "psci";
>  			next-level-cache = <&L2_500>;
>  			qcom,freq-domain = <&cpufreq_hw 0>;
> @@ -139,6 +145,7 @@ CPU6: cpu@600 {
>  			device_type = "cpu";
>  			compatible = "qcom,kryo660";
>  			reg = <0x0 0x600>;
> +			clocks = <&cpufreq_hw 1>;
>  			enable-method = "psci";
>  			next-level-cache = <&L2_600>;
>  			qcom,freq-domain = <&cpufreq_hw 1>;
> @@ -155,6 +162,7 @@ CPU7: cpu@700 {
>  			device_type = "cpu";
>  			compatible = "qcom,kryo660";
>  			reg = <0x0 0x700>;
> +			clocks = <&cpufreq_hw 1>;
>  			enable-method = "psci";
>  			next-level-cache = <&L2_700>;
>  			qcom,freq-domain = <&cpufreq_hw 1>;
> @@ -1383,6 +1391,7 @@ cpufreq_hw: cpufreq@fd91000 {
>  				     <GIC_SPI 31 IRQ_TYPE_LEVEL_HIGH>;
>  			interrupt-names = "dcvsh-irq-0", "dcvsh-irq-1";
>  			#freq-domain-cells = <1>;
> +			#clock-cells = <1>;
>  		};
>  	};
>  

  reply	other threads:[~2023-02-16 10:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-15  7:03 [RESEND PATCH 00/12] arm64: dts: qcom: Supply clock from cpufreq node to CPUs Manivannan Sadhasivam
2023-02-15  7:03 ` [RESEND PATCH 01/12] arm64: dts: qcom: sdm845: " Manivannan Sadhasivam
2023-02-16 10:33   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 02/12] arm64: dts: qcom: sc7280: " Manivannan Sadhasivam
2023-02-16 10:34   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 03/12] arm64: dts: qcom: sm6350: " Manivannan Sadhasivam
2023-02-16 10:35   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 04/12] arm64: dts: qcom: sm8550: " Manivannan Sadhasivam
2023-02-16 10:36   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 05/12] arm64: dts: qcom: sm8250: " Manivannan Sadhasivam
2023-02-16 10:38   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 06/12] arm64: dts: qcom: qdu1000: " Manivannan Sadhasivam
2023-02-16 10:38   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 07/12] arm64: dts: qcom: sc7180: " Manivannan Sadhasivam
2023-02-16 10:38   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 08/12] arm64: dts: qcom: sm8150: " Manivannan Sadhasivam
2023-02-16 10:38   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 09/12] arm64: dts: qcom: sm8350: " Manivannan Sadhasivam
2023-02-16 10:39   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 10/12] arm64: dts: qcom: sc8280xp: " Manivannan Sadhasivam
2023-02-16 10:39   ` Konrad Dybcio
2023-02-15  7:03 ` [RESEND PATCH 11/12] arm64: dts: qcom: sm6375: " Manivannan Sadhasivam
2023-02-16 10:40   ` Konrad Dybcio [this message]
2023-02-15  7:04 ` [RESEND PATCH 12/12] arm64: dts: qcom: sm6115: " Manivannan Sadhasivam
2023-02-16 10:40   ` Konrad Dybcio
2023-02-16 10:32 ` [RESEND PATCH 00/12] arm64: dts: qcom: " Konrad Dybcio
2023-03-15 23:35 ` 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=83e71d32-417b-a343-4a3e-aa7cf0fa6857@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=andersson@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=viresh.kumar@linaro.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).