From: hl@rock-chips.com (Lin Huang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] rk3399 support ddr frequency scaling
Date: Fri, 2 Sep 2016 06:31:20 +0800 [thread overview]
Message-ID: <1472769085-20715-1-git-send-email-hl@rock-chips.com> (raw)
rk3399 platform have dfi controller can monitor ddr load,
and dcf controller to handle ddr register so we can get the
right ddr frequency and make ddr controller happy work(which
will implement in bl31). So we do ddr frequency scaling with
following flow:
kernel bl31
monitor ddr load
|
|
get_target_rate
|
| pass rate to bl31
clk_set_rate(ddr) --------------------->run dcf flow
| |
| |
wait dcf interrupt<-------------------trigger dcf interrupt
|
|
return
Lin Huang (5):
Documentation: bindings: add dt documentation for dfi controller
PM / devfreq: event: support rockchip dfi controller
Documentation: bindings: add dt documentation for rk3399 dmc
PM / devfreq: rockchip: add devfreq driver for rk3399 dmc
drm/rockchip: Add dmc notifier in vop driver
Following patch:
clk: rockchip: add new clock-type for the ddrclk
clk: rockchip: rk3399: add SCLK_DDRCLK ID for ddrc
clk: rockchip: rk3399: add ddrc clock support
have applied to:
http://git.kernel.org/pub/scm/linux/kernel/git/mmind/linux-rockchip.git/v4.9-clk/next
.../bindings/devfreq/event/rockchip-dfi.txt | 19 +
.../devicetree/bindings/devfreq/rk3399_dmc.txt | 173 ++++++++
drivers/devfreq/Kconfig | 11 +
drivers/devfreq/Makefile | 1 +
drivers/devfreq/event/Kconfig | 7 +
drivers/devfreq/event/Makefile | 1 +
drivers/devfreq/event/rockchip-dfi.c | 256 +++++++++++
drivers/devfreq/rk3399_dmc.c | 480 +++++++++++++++++++++
drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 116 +++++
9 files changed, 1064 insertions(+)
create mode 100644 Documentation/devicetree/bindings/devfreq/event/rockchip-dfi.txt
create mode 100644 Documentation/devicetree/bindings/devfreq/rk3399_dmc.txt
create mode 100644 drivers/devfreq/event/rockchip-dfi.c
create mode 100644 drivers/devfreq/rk3399_dmc.c
--
2.6.6
next reply other threads:[~2016-09-01 22:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 22:31 Lin Huang [this message]
2016-09-01 22:31 ` [PATCH 1/5] Documentation: bindings: add dt documentation for dfi controller Lin Huang
2016-09-02 8:50 ` Chanwoo Choi
2016-09-01 22:31 ` [PATCH 2/5] PM / devfreq: event: support rockchip " Lin Huang
2016-09-01 22:31 ` [PATCH 3/5] Documentation: bindings: add dt documentation for rk3399 dmc Lin Huang
2016-09-02 8:53 ` Chanwoo Choi
2016-09-01 22:31 ` [PATCH 4/5] PM / devfreq: rockchip: add devfreq driver " Lin Huang
2016-09-01 23:17 ` Heiko Stübner
2016-09-02 1:46 ` Chanwoo Choi
2016-09-02 1:23 ` kbuild test robot
2016-09-05 0:49 ` Chanwoo Choi
2016-09-01 22:31 ` [PATCH 5/5] drm/rockchip: Add dmc notifier in vop driver Lin Huang
2016-09-02 0:34 ` kbuild test robot
2016-09-02 21:08 [PATCH 0/5] rk3399 support ddr frequency scaling Lin Huang
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=1472769085-20715-1-git-send-email-hl@rock-chips.com \
--to=hl@rock-chips.com \
--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).