From: Niklas Cassel <niklas.cassel@linaro.org>
To: linux-arm-msm@vger.kernel.org
Cc: amit.kucheria@linaro.org, bjorn.andersson@linaro.org,
Niklas Cassel <niklas.cassel@linaro.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] DTS changes to support cpufreq on QCS404
Date: Mon, 25 Nov 2019 15:25:05 +0100 [thread overview]
Message-ID: <20191125142511.681149-1-niklas.cassel@linaro.org> (raw)
The following DTS changes are required to enable cpufreq support on
the QCS404.
Changes since v1:
-Added a cover-letter.
-Swapped order of "pll" and "aux" clocks, in order to not break DT
backwards compatibility. (In case no clock-names are given, "pll" still
has to be the first clock).
-Removed incorrect newline in the middle of the cpu0 DT node.
(This extra newline must have been added by mistake, since no other
cpuX node in the same cluster had this extra newline added.)
Jorge Ramirez-Ortiz (5):
arm64: dts: qcom: msm8916: Add the clocks for the APCS mux/divider
arm64: dts: qcom: qcs404: Add HFPLL node
arm64: dts: qcom: qcs404: Add the clocks for APCS mux/divider
arm64: dts: qcom: qcs404: Add DVFS support
arm64: defconfig: Enable HFPLL
arch/arm64/boot/dts/qcom/msm8916.dtsi | 3 +-
arch/arm64/boot/dts/qcom/qcs404.dtsi | 42 +++++++++++++++++++++++++++
arch/arm64/configs/defconfig | 1 +
3 files changed, 45 insertions(+), 1 deletion(-)
--
2.23.0
next reply other threads:[~2019-11-25 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 14:25 Niklas Cassel [this message]
2019-11-25 14:25 ` [PATCH v2 1/5] arm64: dts: qcom: msm8916: Add the clocks for the APCS mux/divider Niklas Cassel
2019-11-25 14:25 ` [PATCH v2 2/5] arm64: dts: qcom: qcs404: Add HFPLL node Niklas Cassel
2019-11-25 14:25 ` [PATCH v2 3/5] arm64: dts: qcom: qcs404: Add the clocks for APCS mux/divider Niklas Cassel
2019-11-25 14:25 ` [PATCH v2 4/5] arm64: dts: qcom: qcs404: Add DVFS support Niklas Cassel
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=20191125142511.681149-1-niklas.cassel@linaro.org \
--to=niklas.cassel@linaro.org \
--cc=amit.kucheria@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.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).