From: Yangtao Li <tiny.windzz@gmail.com>
To: tiny.windzz@gmail.com, vireshk@kernel.org, nm@ti.com,
sboyd@kernel.org, robh+dt@kernel.org, mark.rutland@arm.com,
maxime.ripard@bootlin.com, wens@csie.org, rjw@rjwysocki.net,
davem@davemloft.net, mchehab+samsung@kernel.org,
gregkh@linuxfoundation.org, nicolas.ferre@microchip.com
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] cpufreq: Add sunxi nvmem based CPU scaling driver
Date: Tue, 9 Apr 2019 13:25:56 -0400 [thread overview]
Message-ID: <20190409172558.18778-1-tiny.windzz@gmail.com> (raw)
Add sunxi nvmem based CPU scaling driver, refers to qcom-cpufreq-kryo.
Yangtao Li (2):
cpufreq: Add sunxi nvmem based CPU scaling driver
dt-bindings: cpufreq: Document operating-points-v2-sunxi-cpu
.../bindings/opp/sunxi-nvmem-cpufreq.txt | 166 +++++++++++++
MAINTAINERS | 7 +
drivers/cpufreq/Kconfig.arm | 10 +
drivers/cpufreq/Makefile | 1 +
drivers/cpufreq/cpufreq-dt-platdev.c | 2 +
drivers/cpufreq/sunxi-cpufreq-nvmem.c | 234 ++++++++++++++++++
6 files changed, 420 insertions(+)
create mode 100644 Documentation/devicetree/bindings/opp/sunxi-nvmem-cpufreq.txt
create mode 100644 drivers/cpufreq/sunxi-cpufreq-nvmem.c
---
v2:
-update changelog
-convert to dev_pm_opp_set_prop_name use instead of dev_pm_opp_set_supported_hw
-some change in OPP Node
---
2.17.0
next reply other threads:[~2019-04-09 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 17:25 Yangtao Li [this message]
2019-04-09 17:25 ` [PATCH v2 1/2] cpufreq: Add sunxi nvmem based CPU scaling driver Yangtao Li
2019-04-10 3:24 ` Viresh Kumar
2019-04-10 17:44 ` Frank Lee
2019-04-09 17:25 ` [PATCH v2 2/2] dt-bindings: cpufreq: Document operating-points-v2-sunxi-cpu Yangtao Li
2019-04-10 3:26 ` Viresh Kumar
2019-04-10 14:56 ` Maxime Ripard
2019-04-10 17:49 ` Frank Lee
2019-04-11 7:49 ` Maxime Ripard
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=20190409172558.18778-1-tiny.windzz@gmail.com \
--to=tiny.windzz@gmail.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.ripard@bootlin.com \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=nm@ti.com \
--cc=rjw@rjwysocki.net \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=vireshk@kernel.org \
--cc=wens@csie.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).