From: Ilia Lin <ilialin@codeaurora.org>
To: ilia.lin@gmail.com, vireshk@kernel.org, nm@ti.com,
sboyd@kernel.org, robh@kernel.org, mark.rutland@arm.com,
rjw@rjwysocki.net
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, ilialin@codeaurora.org
Subject: [PATCH v14 0/2] Kryo CPU scaling driver
Date: Fri, 25 May 2018 15:41:50 +0300 [thread overview]
Message-ID: <1527252112-7015-1-git-send-email-ilialin@codeaurora.org> (raw)
[v14]
* Addressed comment from Sudeep about DT compatible
* Added MAINTAINERS entry
[v13]
* Addressed comment from Sudeep about DT compatible check on init
[v12]
* Addressed comments from Sudeep and Viresh about the single init
[v11]
* Addressed comment from Russel about device_node reference
* Addressed comment from Sudeep about the late_initcall
* Transformed init into probe to take care of deferals
[v10]
* Split the series into domains
* Addressed comments from Viresh and Sudeep about logical CPU numbering.
The qcom-cpufreq-kryo driver is aimed to support different SOC versions.
The driver reads eFuse information and chooses the required OPP subset
by passing the OPP supported-hw parameter.
The series depends on the series from Viresh:
https://patchwork.kernel.org/patch/10418139/
The previous spin was here:
https://patchwork.kernel.org/patch/10424949/
Ilia Lin (2):
cpufreq: Add Kryo CPU scaling driver
dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu
.../devicetree/bindings/opp/kryo-cpufreq.txt | 680 +++++++++++++++++++++
MAINTAINERS | 7 +
drivers/cpufreq/Kconfig.arm | 10 +
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/cpufreq-dt-platdev.c | 3 +
drivers/cpufreq/qcom-cpufreq-kryo.c | 212 +++++++
6 files changed, 913 insertions(+)
create mode 100644 Documentation/devicetree/bindings/opp/kryo-cpufreq.txt
create mode 100644 drivers/cpufreq/qcom-cpufreq-kryo.c
--
1.9.1
next reply other threads:[~2018-05-25 12:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 12:41 Ilia Lin [this message]
2018-05-25 12:41 ` [PATCH v14 1/2] cpufreq: Add Kryo CPU scaling driver Ilia Lin
2018-05-28 5:03 ` Viresh Kumar
2018-05-25 12:41 ` [PATCH v14 2/2] dt-bindings: cpufreq: Document operating-points-v2-kryo-cpu Ilia Lin
-- strict thread matches above, loose matches on Subject: below --
2018-05-25 12:07 [PATCH v14 0/2] Kryo CPU scaling driver Ilia Lin
2018-05-29 11:11 ` Amit Kucheria
2018-05-30 8:08 ` Rafael J. Wysocki
2018-05-30 9:15 ` Viresh Kumar
2018-05-30 11:06 ` Ilia Lin
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=1527252112-7015-1-git-send-email-ilialin@codeaurora.org \
--to=ilialin@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=ilia.lin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=vireshk@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.