From: Tengfei Fan <quic_tengfan@quicinc.com>
To: <rafael@kernel.org>, <viresh.kumar@linaro.org>, <robh@kernel.org>,
<krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>
Cc: <manivannan.sadhasivam@linaro.org>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-msm@vger.kernel.org>,
Tengfei Fan <quic_tengfan@quicinc.com>
Subject: [PATCH 0/3] arm64: qcom: Add cpufreq and clock support
Date: Wed, 24 Apr 2024 18:15:00 +0800 [thread overview]
Message-ID: <20240424101503.635364-1-quic_tengfan@quicinc.com> (raw)
Add cpufreq and clock support for SM4450 platform.
Signed-off-by: Tengfei Fan <quic_tengfan@quicinc.com>
---
Tengfei Fan (3):
dt-bindings: cpufreq: cpufreq-qcom-hw: Add SM4450 compatibles
arm64: dts: qcom: sm4450: Add cpufreq support
arm64: dts: qcom: sm4450: Supply clock from cpufreq node to CPUs
.../bindings/cpufreq/cpufreq-qcom-hw.yaml | 2 +
arch/arm64/boot/dts/qcom/sm4450.dtsi | 37 +++++++++++++++++++
2 files changed, 39 insertions(+)
base-commit: a59668a9397e7245b26e9be85d23f242ff757ae8
--
2.25.1
next reply other threads:[~2024-04-24 10:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 10:15 Tengfei Fan [this message]
2024-04-24 10:15 ` [PATCH 1/3] dt-bindings: cpufreq: cpufreq-qcom-hw: Add SM4450 compatibles Tengfei Fan
2024-04-24 17:03 ` Bjorn Andersson
2024-04-24 22:08 ` Rob Herring
2024-04-25 5:21 ` Viresh Kumar
2024-04-24 10:15 ` [PATCH 2/3] arm64: dts: qcom: sm4450: Add cpufreq support Tengfei Fan
2024-04-24 23:41 ` Dmitry Baryshkov
2024-04-25 3:18 ` Tengfei Fan
2024-04-24 10:15 ` [PATCH 3/3] arm64: dts: qcom: sm4450: Supply clock from cpufreq node to CPUs Tengfei Fan
2024-04-24 11:23 ` Dmitry Baryshkov
2024-04-25 3:17 ` Tengfei Fan
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=20240424101503.635364-1-quic_tengfan@quicinc.com \
--to=quic_tengfan@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=rafael@kernel.org \
--cc=robh@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 read-only IMAP folder(s) and NNTP newsgroup(s).