public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Andy Gross <agross@kernel.org>,
	Bjorn Andersson <andersson@kernel.org>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: [PATCH 8/8] arm64: dts: qcom: sm8150: Add SoC-specific compatible to cpufreq_hw
Date: Wed, 08 Mar 2023 02:27:05 +0100	[thread overview]
Message-ID: <20230308-topic-cpufreq_bindings-v1-8-3368473ec52d@linaro.org> (raw)
In-Reply-To: <20230308-topic-cpufreq_bindings-v1-0-3368473ec52d@linaro.org>

Add a SoC-specific compatbile to cpufreq_hw for compliancy with bindings.

Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
---
 arch/arm64/boot/dts/qcom/sm8150.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/arch/arm64/boot/dts/qcom/sm8150.dtsi b/arch/arm64/boot/dts/qcom/sm8150.dtsi
index fd20096cfc6e..e7e66bc3e6c4 100644
--- a/arch/arm64/boot/dts/qcom/sm8150.dtsi
+++ b/arch/arm64/boot/dts/qcom/sm8150.dtsi
@@ -4263,7 +4263,7 @@ osm_l3: interconnect@18321000 {
 		};
 
 		cpufreq_hw: cpufreq@18323000 {
-			compatible = "qcom,cpufreq-hw";
+			compatible = "qcom,sm8150-cpufreq-hw", "qcom,cpufreq-hw";
 			reg = <0 0x18323000 0 0x1400>, <0 0x18325800 0 0x1400>,
 			      <0 0x18327800 0 0x1400>;
 			reg-names = "freq-domain0", "freq-domain1",

-- 
2.39.2


  parent reply	other threads:[~2023-03-08  1:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08  1:26 [PATCH 0/8] qcom-cpufreq-hw binding improvements Konrad Dybcio
2023-03-08  1:26 ` [PATCH 1/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Allow just 1 frequency domain Konrad Dybcio
2023-03-16 22:36   ` Rob Herring
2023-03-08  1:26 ` [PATCH 2/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Sanitize data per compatible Konrad Dybcio
2023-03-16 22:39   ` Rob Herring
2023-03-08  1:27 ` [PATCH 3/8] dt-bindings: cpufreq: cpufreq-qcom-hw: Add QCM2290 Konrad Dybcio
2023-03-16 22:39   ` Rob Herring
2023-03-08  1:27 ` [PATCH 4/8] arm64: dts: qcom: sc7180: Add SoC-specific compatible to cpufreq_hw Konrad Dybcio
2023-03-08  1:27 ` [PATCH 5/8] arm64: dts: qcom: sdm845: " Konrad Dybcio
2023-03-08  1:27 ` [PATCH 6/8] arm64: dts: qcom: sm6115: " Konrad Dybcio
2023-03-08  1:27 ` [PATCH 7/8] arm64: dts: qcom: sm6350: " Konrad Dybcio
2023-03-08 10:35   ` Luca Weiss
2023-03-08  1:27 ` Konrad Dybcio [this message]
2023-03-22 14:45 ` (subset) [PATCH 0/8] qcom-cpufreq-hw binding improvements Bjorn Andersson
2023-03-30  3:59 ` Viresh Kumar

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=20230308-topic-cpufreq_bindings-v1-8-3368473ec52d@linaro.org \
    --to=konrad.dybcio@linaro.org \
    --cc=agross@kernel.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=linux-pm@vger.kernel.org \
    --cc=mani@kernel.org \
    --cc=rafael@kernel.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