From: icenowy@aosc.io (Icenowy Zheng)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC
Date: Sat, 23 Sep 2017 08:15:28 +0800 [thread overview]
Message-ID: <20170923001531.14285-1-icenowy@aosc.io> (raw)
This patchset imports simple DVFS support for Allwinner A64 SoC.
As the thermal sensor driver is not yet implemented and some boards
have still no AXP PMIC support, now only two OPPs are present --
648MHz at 1.04V and 816MHz at 1.1V to prevent overheat or undervoltage.
PATCH 1 is a fix to the CCU driver of A64, and the remaining patches
set up the device tree bits of the DVFS on Pine64.
Icenowy Zheng (3):
clk: sunxi-ng: add mux and pll notifiers for A64 CPU clock
arm64: allwinner: a64: add CPU opp table
arm64: allwinner: a64: set CPU regulator for Pine64
.../arm64/boot/dts/allwinner/sun50i-a64-pine64.dts | 4 ++++
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 24 +++++++++++++++++++
drivers/clk/sunxi-ng/ccu-sun50i-a64.c | 28 +++++++++++++++++++++-
3 files changed, 55 insertions(+), 1 deletion(-)
--
2.13.5
next reply other threads:[~2017-09-23 0:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-23 0:15 Icenowy Zheng [this message]
2017-09-23 0:15 ` [PATCH 1/3] clk: sunxi-ng: add mux and pll notifiers for A64 CPU clock Icenowy Zheng
2017-09-28 10:27 ` Maxime Ripard
2017-09-28 10:42 ` icenowy at aosc.io
2017-09-28 14:20 ` Maxime Ripard
2017-09-28 14:24 ` icenowy at aosc.io
2017-09-28 14:31 ` Maxime Ripard
2017-09-23 0:15 ` [PATCH 2/3] arm64: allwinner: a64: add CPU opp table Icenowy Zheng
2017-09-25 17:38 ` [linux-sunxi] " Samuel Holland
2017-09-23 0:15 ` [PATCH 3/3] arm64: allwinner: a64: set CPU regulator for Pine64 Icenowy Zheng
2017-09-25 10:10 ` [PATCH 0/3] Simple DVFS support for Allwinner A64 SoC Maxime Ripard
2017-09-25 10:12 ` Icenowy Zheng
2017-09-25 10:27 ` Maxime Ripard
2017-09-25 10:29 ` [linux-sunxi] " Icenowy Zheng
2017-09-25 10:43 ` Maxime Ripard
2017-09-27 11:51 ` icenowy at aosc.io
2017-09-28 10:28 ` 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=20170923001531.14285-1-icenowy@aosc.io \
--to=icenowy@aosc.io \
--cc=linux-arm-kernel@lists.infradead.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).