From: Christian Marangi <ansuelsmth@gmail.com>
To: Ilia Lin <ilia.lin@kernel.org>, Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
"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>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
Sricharan Ramabadhran <quic_srichara@quicinc.com>,
Christian Marangi <ansuelsmth@gmail.com>,
linux-pm@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v6 0/4] cpufreq: qcom-nvmem: add support for ipq806x
Date: Fri, 13 Oct 2023 19:38:50 +0200 [thread overview]
Message-ID: <20231013173854.7399-1-ansuelsmth@gmail.com> (raw)
The first patch of this series was split to a separate series as it
doesn't depend on [1] and can be applied right away,
[1] introduced some breaking change to function that ipq806x, ipq807x
patch was dropped to permit an easier rebase and merge of both.
This small series adds support for ipq806x qcom-cpufreq-nvmem driver.
Special function are required to make use of the opp-supported-hw
binding by hardcoding custom bits based on the qcom SoC ID.
The qcom-cpufreq-nvmem driver had recent changes to also improve
support for apq8064. Because of this, this series depends on a
just merged series.
Depends on [1].
[1] https://lore.kernel.org/linux-pm/20231010063235.rj2ehxugtjr5x2xr@vireshk-i7/T/#t
Christian Marangi (4):
dt-bindings: cpufreq: qcom-cpufreq-nvmem: Document krait-cpu
dt-bindings: opp: opp-v2-kryo-cpu: Document named opp-microvolt
property
cpufreq: qcom-nvmem: add support for IPQ8064
ARM: dts: qcom: ipq8064: Add CPU OPP table
.../bindings/cpufreq/qcom-cpufreq-nvmem.yaml | 4 +-
.../bindings/opp/opp-v2-kryo-cpu.yaml | 22 ++++++
arch/arm/boot/dts/qcom/qcom-ipq8062.dtsi | 30 +++++++++
arch/arm/boot/dts/qcom/qcom-ipq8064.dtsi | 67 +++++++++++++++++++
arch/arm/boot/dts/qcom/qcom-ipq8065.dtsi | 65 ++++++++++++++++++
drivers/cpufreq/qcom-cpufreq-nvmem.c | 67 ++++++++++++++++++-
6 files changed, 253 insertions(+), 2 deletions(-)
--
2.40.1
next reply other threads:[~2023-10-13 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 17:38 Christian Marangi [this message]
2023-10-13 17:38 ` [PATCH v6 1/4] dt-bindings: cpufreq: qcom-cpufreq-nvmem: Document krait-cpu Christian Marangi
2023-10-17 19:13 ` Rob Herring
2023-10-13 17:38 ` [PATCH v6 2/4] dt-bindings: opp: opp-v2-kryo-cpu: Document named opp-microvolt property Christian Marangi
2023-10-13 17:38 ` [PATCH v6 3/4] cpufreq: qcom-nvmem: add support for IPQ8064 Christian Marangi
2023-10-26 20:01 ` Konrad Dybcio
2023-10-13 17:38 ` [PATCH v6 4/4] ARM: dts: qcom: ipq8064: Add CPU OPP table Christian Marangi
2023-10-19 6:46 ` [PATCH v6 0/4] cpufreq: qcom-nvmem: add support for ipq806x Viresh Kumar
2023-10-19 10:52 ` Christian Marangi
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=20231013173854.7399-1-ansuelsmth@gmail.com \
--to=ansuelsmth@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@kernel.org \
--cc=konrad.dybcio@linaro.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=nm@ti.com \
--cc=quic_srichara@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@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).