From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: agross@kernel.org, bjorn.andersson@linaro.org,
ilia.lin@kernel.org, rafael@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
bryan.odonoghue@linaro.org, robh+dt@kernel.org,
krzk+dt@kernel.org, devicetree@vger.kernel.org
Subject: [PATCH 2/5] dt-bindings: opp: Add msm8939 to the compatible list
Date: Mon, 18 Apr 2022 17:22:23 +0100 [thread overview]
Message-ID: <20220418162226.2983117-3-bryan.odonoghue@linaro.org> (raw)
In-Reply-To: <20220418162226.2983117-1-bryan.odonoghue@linaro.org>
msm8939 will uses this driver instead of the generic dt-cpufreq. Add to the
compatible list.
Cc: ilia.lin@kernel.org
Cc: robh+dt@kernel.org
Cc: krzk+dt@kernel.org
Cc: devicetree@vger.kernel.org
Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
---
.../devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml b/Documentation/devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml
index 5eb1dba13fe2..7efae476c02e 100644
--- a/Documentation/devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml
+++ b/Documentation/devicetree/bindings/cpufreq/qcom-cpufreq-nvmem.yaml
@@ -25,6 +25,7 @@ select:
- qcom,apq8064
- qcom,apq8096
- qcom,ipq8064
+ - qcom,msm8939
- qcom,msm8960
- qcom,msm8974
- qcom,msm8996
--
2.35.1
next prev parent reply other threads:[~2022-04-18 16:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220418162226.2983117-1-bryan.odonoghue@linaro.org>
2022-04-18 16:22 ` [PATCH 1/5] dt-bindings: opp: Add missing compat devices Bryan O'Donoghue
2022-04-26 20:09 ` Rob Herring
2022-04-18 16:22 ` Bryan O'Donoghue [this message]
2022-04-26 20:10 ` [PATCH 2/5] dt-bindings: opp: Add msm8939 to the compatible list Rob Herring
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=20220418162226.2983117-3-bryan.odonoghue@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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).